| 2.1 | Approval of the agenda | |
|---|---|---|
| R2-2002500 | Agenda for RAN2#109bis-e | Chairman |
| 2.2 | Approval of the report of the previous meeting | |
| R2-2002501 | RAN2#109-e Meeting Report | MCC |
| 2.4 | Others | |
| R2-2003824 | RAN2 109bis-e e-meeting Methods and Guidance | Chairman |
| 3 | Incoming liaisons | |
| R2-2002519 | LS on updated Rel-16 LTE and NR parameter lists (R1-2001479; contact: Qualcomm) | RAN1 |
| R2-2002536 | Reply LS on UAV positioning (S1-201089; contact: InterDigital) | SA1 |
| R2-2002539 | LS on 5GC assisted cell selection for accessing network slice (S2-2001728; contact: ZTE) | SA2 |
| R2-2002542 | Response LS on the “LS OUT on Location of UEs and associated key issues” (S3i200056; contact: Rogers) | SA3-LI |
| R2-2002546 | LS on Requirements on positioning for UAS (S6-200269; contact: InterDigital) | SA6 |
| R2-2002547 | LS/o on synchronization of Y.DNI-fr “Framework and Requirements of Decentralized Trustworthy Network Infrastructure” in Q2/13 (SG13-LS157; contact: China Telecom, Huawei) | ITU-T SG13 |
| R2-2002548 | Reply LS to extend the scope of eV2X (SP-191379; contact: Telecom Italia) | SA |
| R2-2002549 | Reply LS on support for eCall over NR (SP-200287; contact: Qualcomm) | SA |
| R2-2002553 | [Reserved for LSin] | RANX |
| R2-2002554 | [Reserved for LSin] | RANX |
| R2-2002922 | [DRAFT] Response LS on the “LS OUT on Location of UEs and associated key issues” | THALES |
| R2-2004190 | [DRAFT] Response LS on the “LS OUT on Location of UEs and associated key issues” | THALES |
| R2-2004266 | Response LS on the “LS OUT on Location of UEs and associated key issues” | RAN2 |
| 4.1 | NB-IoT corrections Rel-15 and earlier | |
| R2-2003245 | Optimisation on trigger for dedicated SR with HARQ-ACK | ZTE Corporation, Sanechips, MediaTek Inc. |
| R2-2003246 | Clarification on RLC UM SN size for NB-IoT | Huawei, HiSilicon |
| R2-2003254 | Optimisation on trigger for dedicated SR with HARQ-ACK | ZTE Corporation, Sanechips, MediaTek Inc. |
| R2-2003256 | Optimisation on trigger for dedicated SR with HARQ-ACK | ZTE Corporation, Sanechips, MediaTek Inc. |
| R2-2003619 | Discussion on dedicated frequency search after connection rejection | MediaTek Inc. |
| R2-2003621 | Cell selection on the dedicated frequency after RRC connection rejection for NB-IoT in 36.304 | MediaTek Inc. |
| R2-2003622 | Cell selection on the dedicated frequency after RRC connection rejection for NB-IoT in 36.331 | MediaTek Inc. |
| R2-2004036 | Report of [AT109e][301][ NBIOT R14] Clarification on polling bit for RRCConnectionRelease (Huawei) | Huawei (offline email discussion rapporteur) |
| R2-2004037 | Report of [AT109bis-e][302][NBIOT]Trigger for dedicated SR with HARQ-ACK (ZTE) | ZTE |
| R2-2004038 | Report of [AT109bis-e][303][NBIOT] Cell selection on the dedicated frequency after RRC connection rejection for NB-IoT (Mediatek) | MediaTek (offline email discussion rapporteur) |
| R2-2004056 | Clarification on RLC UM SN size for NB-IoT | Huawei, HiSilicon |
| 4.2 | eMTC corrections Rel-15 and earlier | |
| R2-2003189 | Correction on reception type combination for eMTC | ZTE Corporation, Sanechips, Sequans Communications |
| R2-2003190 | Correction on reception type combination for eMTC | ZTE Corporation, Sanechips, Sequans Communications |
| R2-2003222 | Correction on reception type combination for eMTC | ZTE Corporation, Sanechips, Sequans Communications |
| R2-2003228 | Correction on reception type combination for eMTC | ZTE Corporation, Sanechips, Sequans Communications |
| R2-2003342 | Adding Reception Type for uplink HARQ ACK feedback for Rel-15 eMTC | Huawei, HiSilicon |
| R2-2003916 | Report of [AT109bis-e][401][eMTC] Correction on reception type combination (ZTE) | ZTE (email discussion rapporteur) |
| R2-2003917 | Report [AT109bis-e][402][eMTC] Adding Reception Type for uplink HARQ ACK feedback for Rel-15 eMTC (Huawei) | Huawei (offline email discussion rapporteur) |
| R2-2003933 | Adding Reception Type for uplink HARQ ACK feedback for Rel-15 eMTC | Huawei, HiSilicon |
| R2-2003937 | Correction on reception type combination for eMTC | ZTE Corporation, Sanechips, Sequans Communications |
| 4.3 | V2X and Sidelink corrections Rel-15 and earlier | |
| R2-2003641 | Correction on Uu and PC5 prioritization | ASUSTeK |
| R2-2003642 | Correction on Uu and PC5 prioritization | ASUSTeK |
| 4.5 | Other LTE corrections Rel-15 and earlier | |
| R2-2002619 | Correction on SRB duplication | OPPO |
| R2-2002620 | Correction on SRB duplication | OPPO |
| R2-2003147 | Clarification to UE capabilities for non-contiguous intra-band CA | Nokia, Nokia Shanghai Bell |
| R2-2003148 | Clarification to UE capabilities for non-contiguous intra-band CA | Nokia, Nokia Shanghai Bell |
| R2-2003149 | Clarification to UE capabilities for non-contiguous intra-band CA | Nokia, Nokia Shanghai Bell |
| R2-2003150 | Clarification to UE capabilities for non-contiguous intra-band CA | Nokia, Nokia Shanghai Bell |
| R2-2003151 | Clarification to UE capabilities for non-contiguous intra-band CA | Nokia, Nokia Shanghai Bell |
| R2-2003152 | Clarification on codebook-HARQ-ACK-r13 capability for CA with more than 5CCs | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R2-2003153 | Clarification on codebook-HARQ-ACK-r13 capability for CA with more than 5CCs | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R2-2003154 | Clarification on codebook-HARQ-ACK-r13 capability for CA with more than 5CCs | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R2-2003155 | Clarification on codebook-HARQ-ACK-r13 capability for CA with more than 5CCs | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R2-2003232 | Minor changes collected by Rapporteur | Samsung Telecommunications |
| R2-2003233 | Minor changes collected by Rapporteur | Samsung Telecommunications |
| R2-2003390 | Minor changes collected by Rapporteur | Samsung Telecommunications |
| R2-2003391 | Minor changes collected by Rapporteur | Samsung Telecommunications |
| R2-2003451 | Correction on autonomous measurment gap release | Huawei, HiSilicon |
| R2-2003452 | Correction on autonomous measurment gap release | Huawei, HiSilicon |
| R2-2003453 | Correction on autonomous measurment gap release | Huawei, HiSilicon |
| R2-2003548 | Clarification on UE capability for intra-band non-continuous CA | Huawei, Hisilicon |
| R2-2003549 | Clarification on UE capability for intra-band non-continuous CA | Huawei, Hisilicon |
| R2-2003550 | Clarification on UE capability for intra-band non-continuous CA | Huawei, Hisilicon |
| R2-2003551 | Clarification on UE capability for intra-band non-continuous CA | Huawei, Hisilicon |
| R2-2003552 | Clarification on UE capability for intra-band non-continuous CA | Huawei, Hisilicon |
| R2-2003553 | Clarification on UE capability for intra-band non-continuous CA | Huawei, Hisilicon |
| R2-2003554 | Clarification on UE capability for intra-band non-continuous CA | Huawei, Hisilicon |
| R2-2003569 | Discussion on Need code for CMAS | Huawei, HiSilicon |
| R2-2003570 | Correction on Need code for CMAS | Huawei, HiSilicon |
| R2-2003571 | Correction on Need code for CMAS | Huawei, HiSilicon |
| R2-2003572 | Correction on Need code for CMAS | Huawei, HiSilicon |
| R2-2003573 | Correction on Need code for CMAS | Huawei, HiSilicon |
| R2-2003841 | Summary of LTE contributions in AI 4.5 | Nokia (RAN2 VC) |
| R2-2003859 | Clarification on codebook-HARQ-ACK-r13 capability for CA with more than 5CCs | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| 5.1 | Organisational | |
| R2-2002525 | Reply LS on Tx DC location (R4-1915361; contact: Huawei) | RAN4 |
| R2-2004252 | LS on default RE mapping patterns (R1-2002828; contact: Ericsson) | RAN1 |
| 5.2.2 | Stage 2 corrections for TS 37.340 | |
| R2-2002988 | TS 37.340 Clarifying the options for PDCP version change | Nokia, Nokia Shanghai Bell |
| R2-2003539 | Correction on MAC description in TS 37.340 | Huawei, HiSilicon |
| R2-2003540 | Correction on MAC description in TS 37.340 | Huawei, HiSilicon |
| R2-2003685 | Clarification on PDCP version change | Huawei, HiSilicon |
| R2-2003686 | Clarification on PDCP version change | Huawei, HiSilicon |
| R2-2003687 | Clarification on PDCP version change | Huawei, HiSilicon |
| R2-2003688 | Clarification on PDCP version change | Huawei, HiSilicon |
| R2-2003689 | Clarification on the SCG configuration handing in RRC_INACTIVE | Huawei, HiSilicon |
| R2-2004115 | Summary for offline [002][NR15] 37340 corrections | Huawei |
| R2-2004239 | Summary from [AT109bis-e][001][NR15] PDCP version change (Ericsson) | Ericsson |
| 5.2.3 | Positioning | |
| R2-2003479 | Correction to periodic reporting | Huawei, HiSilicon |
| R2-2003482 | Correction to periodic reporting | Huawei, HiSilicon |
| 5.3.1 | MAC | |
| R2-2002515 | Reply LS on UL skipping (R1-2001376; contact: vivo) | RAN1 |
| R2-2002612 | Clarification on the Random Access parameters for BFR | Samsung |
| R2-2002780 | Discussion on the UL skipping | vivo |
| R2-2003481 | Correction on the RACH parameters for BFR | Huawei, HiSilicon |
| R2-2003484 | Correction on the RACH parameters for BFR | Huawei, HiSilicon |
| R2-2003594 | CR to 38.321 on UCI transmission in the case the overlapping PUSCH transmission is skipped | ZTE, Sanechips |
| R2-2003610 | Further discussion on UL skipping for UCI multiplexing | Huawei, HiSilicon |
| R2-2003643 | UL grant overridden between configured grant and RAR grant | ASUSTeK |
| R2-2003835 | Report of [AT109bis-e][003][NR15] MAC Maintenance (Samsung) | Samsung |
| 5.3.2 | RLC | |
| R2-2002762 | RLC status report truncation | Qualcomm Incorporated |
| R2-2002767 | RLC status report truncation | Qualcomm Incorporated |
| R2-2003766 | RLC status report truncation | Qualcomm Incorporated, Verizon Wireless |
| R2-2003767 | RLC status report truncation | Qualcomm Incorporated, Verizon Wireless |
| R2-2004134 | Summary of [AT109bis-e][004][NR15] RLC and PDCP RLC and PDCP Maintenance | Qualcomm |
| 5.3.3 | PDCP | |
| R2-2002823 | Ordering of PDCP SN and RLC SN | Qualcomm Incorporated |
| R2-2002824 | Ordering of PDCP SN and RLC SN | Qualcomm Incorporated |
| R2-2002825 | PDCP Recovery conditions | Qualcomm Incorporated |
| 5.4.1.1 | Connection control | |
| R2-2002508 | Reply LS for clarification of PUCCH configuration (R1-2001306; contact: Huawei) | RAN1 |
| R2-2002540 | Reply LS on Handling of UE radio network capabilities in 4G and 5G (S3-194488; contact: Intel) | SA3 |
| R2-2002551 | Reply LS for clarification of PUCCH configuration (R1-2001306; contact: Huawei) | RAN1 |
| R2-2002681 | Discussion on recursion in RRC | Nokia, Nokia Shanghai Bell |
| R2-2002682 | Clarification on recursion in RRC messages | Nokia, Nokia Shanghai Bell, Apple |
| R2-2002683 | Clarification on recursion in RRC messages | Nokia, Nokia Shanghai Bell, Apple |
| R2-2002697 | Clarification on SRS-CarrierSwitching structure | ZTE Corporation, Sanechips, Qualcomm Incorporated |
| R2-2002698 | CR on SRS-CarrierSwitching | ZTE Corporation, Sanechips, Qualcomm Incorporated |
| R2-2002763 | Clarification on the presence of ssb-perRACH-Occasion for the CSI-RS based CFRA | ZTE Corporation, Sanechips, Ericsson (Rapporteur) |
| R2-2002786 | Fully Utilize of RACH Preamble Distribution | CATT |
| R2-2002787 | Correction on CSI-ResourceConfig | CATT |
| R2-2002886 | Corrections on the allowedSCS-List and AllowedServingCells in LogicalChannelConfig | Samsung |
| R2-2002917 | Clarification on the presence of ssb-perRACH-Occasion for the CSI-RS based CFRA | ZTE Corporation, Sanechips, Ericsson (Rapporteur) |
| R2-2002948 | Change of pdcp-Duplication at RRC Reconfiguration | Samsung |
| R2-2002949 | Clarification on pdcp-Duplication at RRC Reconfiguration | Samsung |
| R2-2002987 | TS 36.331 Clarifying the options for PDCP version change | Nokia, Nokia Shanghai Bell |
| R2-2003071 | Clarification on recursion in RRC messages | Nokia, Nokia Shanghai Bell, Apple |
| R2-2003196 | Correction related to RRC reconfiguration complete | Ericsson |
| R2-2003197 | Correction related to RRC reconfiguration complete | Ericsson |
| R2-2003244 | Clarification on the using of RRCSetup in 38.331 | China Unicom, Huawei, HiSilicon |
| R2-2003334 | Clarification on avoiding keystream repeat due to COUNT reuse | Qualcomm Incorporated, Ericsson, Vodafone, NTT DOCOMO |
| R2-2003335 | Clarification on avoiding keystream repeat due to COUNT reuse | Qualcomm Incorporated, Ericsson, Vodafone, NTT DOCOMO |
| R2-2003336 | Clarification on avoiding keystream repeat due to COUNT reuse | Qualcomm Incorporated, Ericsson, Vodafone, NTT DOCOMO |
| R2-2003337 | Clarification on avoiding keystream repeat due to COUNT reuse | Qualcomm Incorporated, Ericsson, Vodafone, NTT DOCOMO |
| R2-2003386 | Piggybacking of NAS PDUs including Service Accept | Ericsson |
| R2-2003480 | Correction on PUSCH-less uplink carrier | Huawei, HiSilicon |
| R2-2003483 | Correction on PUSCH-less uplink carrier | Huawei, HiSilicon |
| R2-2003537 | Correction on PUCCH configuration | Huawei, HiSilicon |
| R2-2003538 | Correction on PUCCH configuration | Huawei, HiSilicon |
| R2-2003670 | Discussion on radio bear configuration in MR-DC | Google Inc. |
| R2-2003671 | Correction to RadioBearerConfig | Google Inc. |
| R2-2003690 | Correction on the need for reconfiguration with sync in (NG)EN-DC, NR-DC and NE-DC | Huawei, HiSilicon, Ericsson |
| R2-2003691 | Correction on the need for reconfiguration with sync in (NG)EN-DC, NR-DC and NE-DC | Huawei, HiSilicon, Ericsson |
| R2-2003692 | Correction on reestablishRLC | Huawei, HiSilicon |
| R2-2003693 | Correction on reestablishRLC | Huawei, HiSilicon |
| R2-2003694 | Clarfication on Scell release | Huawei, HiSilicon |
| R2-2003695 | Clarfication on Scell release | Huawei, HiSilicon |
| R2-2003697 | Potential issue on the Counter Check in (NG)EN-DC and NR standalone | Huawei, HiSilicon |
| R2-2003698 | Draft LS to SA3 on potential issue of Counter Check | Huawei, HiSilicon |
| R2-2003778 | Clarification on the using of RRCSetup in 38.331 | China Unicom, Huawei, HiSilicon |
| R2-2003837 | Summary of [AT109bis-e][008][NR15] Conn Control Miscellaneous I | Ericsson |
| R2-2004116 | Summary for offline [005][NR15] L1 Configuration | Huawei, ZTE |
| R2-2004118 | Offline-006: L2 Configuration | Samsung, ZTE Corporation, Sanechips |
| R2-2004119 | Clarification on pdcp-Duplication at RRC Reconfiguration | Samsung |
| R2-2004135 | Correction on PUCCH configuration | Huawei, HiSilicon |
| R2-2004136 | Correction on PUCCH configuration | Huawei, HiSilicon |
| R2-2004138 | Clarification on pdcp-Duplication at RRC Reconfiguration | Samsung |
| R2-2004139 | Clarification on pdcp-Duplication at RRC Reconfiguration | Samsung |
| R2-2004140 | Clarification on pdcp-Duplication at RRC Reconfiguration | Samsung |
| R2-2004194 | [DRAFT] LS on Piggybacking of Service Accept | Ericsson |
| R2-2004204 | [AT109bis-e][007][NR15] Security | Qualcomm |
| R2-2004269 | Correction on the need for reconfiguration with sync in (NG)EN-DC, NR-DC and NE-DC | Huawei, HiSilicon, Ericsson |
| R2-2004270 | Correction on the need for reconfiguration with sync in (NG)EN-DC, NR-DC and NE-DC | Huawei, HiSilicon, Ericsson |
| 5.4.1.2 | RRM and Measurements and Measurement Coordination | |
| R2-2002692 | Clarification for SSB-ToMeasure | Nokia, Nokia Shanghai Bell |
| R2-2002693 | Clarification of SSB-ToMeasure | Nokia, Nokia Shanghai Bell |
| R2-2003699 | Correction to inter-RAT SFTD measurements | Huawei, HiSiicon |
| R2-2003700 | Correction to inter-RAT SFTD measurements | Huawei, HiSiicon |
| R2-2003701 | Correction to inter-RAT SFTD measurements | Huawei, HiSilicon |
| R2-2003702 | Correction to inter-RAT SFTD measurements | Huawei, HiSilicon |
| R2-2003734 | Correction to inter-RAT SFTD measurements | Huawei, HiSilicon |
| R2-2003735 | Correction to inter-RAT SFTD measurements | Huawei, HiSilicon |
| R2-2004113 | Summary of [AT109bis-e][010][NR15] Measurements (Huawei, Nokia) | Nokia, Nokia Shanghai Bell, Huawei, HiSilicon |
| 5.4.1.3 | System information | |
| R2-2002818 | Clarification on the essential fields in SIB1 | Apple |
| R2-2002819 | Clarification on the essential fields in SIB1 | Apple |
| R2-2003282 | Clarification for SIB6, SIB7 and SIB8 acquisition during a measurement gap | Ericsson, Qualcomm, NTT DOCOMO INC, Nokia, InterDigital |
| R2-2003283 | ETWS and CMAS acquisition during measurement gaps | Ericsson, Qualcomm, NTT DOCOMO INC, Nokia, InterDigital |
| R2-2003527 | Clarification for SIB6, SIB7 and SIB8 acquisition during a measurement gap | Ericsson, Qualcomm, NTT DOCOMO INC, Nokia, InterDigital |
| R2-2004157 | Summary of [AT109bis-e][011][NR15] System Information and Other | Huawei |
| R2-2004260 | Clarification for SIB6, SIB7 and SIB8 acquisition during a measurement gap | Ericsson, Qualcomm, NTT DOCOMO INC, Nokia, InterDigital |
| R2-2004261 | Clarification for SIB6, SIB7 and SIB8 acquisition during a measurement gap | Ericsson, Qualcomm, NTT DOCOMO INC, Nokia, InterDigital |
| 5.4.1.4 | Inter-Node RRC messages | |
| R2-2003191 | Correction on MN-SN measurements coordination in INM | Ericsson |
| R2-2003192 | Correction on MN-SN measurements coordination in INM | Ericsson |
| R2-2003193 | Correction on MN-SN measurements coordination in INM | Ericsson |
| R2-2003194 | Correction on MN-SN measurements coordination in INM | Ericsson |
| R2-2003195 | Remaining issues on MN-SN measurement coordination in INM | Ericsson |
| R2-2003753 | Introduce RRC version for source configuration | Google Inc. |
| R2-2003838 | Summary of [AT109bis-e][012][NR15] Inter Node Coord | Ericsson |
| R2-2004249 | Correction on MN-SN measurements coordination in INM | Ericsson |
| R2-2004250 | Correction on MN-SN measurements coordination in INM | Ericsson |
| 5.4.1.5 | Other | |
| R2-2003696 | Mandatory presence of a need M field due to a child presence condition | Huawei, HiSilicon |
| 5.4.2 | LTE changes related to NR | |
| R2-2002597 | Correction to shortResumeMAC-I calculation for RRC_INACTIVE | Ericsson |
| R2-2002645 | Correction to shortResumeMAC-I calculation for RRC_INACTIVE | Ericsson |
| R2-2002788 | Correction on Release of EN-DC | CATT |
| R2-2002985 | Avoiding security risk for RLC AM bearers during termination point change | Nokia, Nokia Shanghai Bell, Deutsche Telekom |
| R2-2002986 | Avoiding security risk for RLC AM bearers during termination point change | Nokia, Nokia Shanghai Bell, Deutsche Telekom |
| R2-2003156 | Clarification to TTI bundling configuration in NE-DC | Nokia, Nokia Shanghai Bell |
| R2-2003157 | Clarification to TTI bundling configuration in NE-DC | Nokia, Nokia Shanghai Bell |
| R2-2003399 | PDCP version change with or without handover | Ericsson, Intel Corporation |
| R2-2003400 | Allowing PDCP version change without handover | Ericsson, Intel Corporation |
| R2-2003401 | Allowing PDCP version change without handover | Ericsson, Intel Corporation |
| R2-2003402 | Allowing PDCP version change without handover | Ericsson, Intel Corporation |
| R2-2003405 | Allowing PDCP version change without handover | Ericsson, Intel Corporation |
| R2-2003684 | UE measurement capability requirements for NR | Google Inc. |
| R2-2004102 | Summary of [AT109bis-e][059][NR15] LTE changes related to NR | Ericsson |
| R2-2004191 | Allowing PDCP version change without handover | Ericsson, Intel Corporation |
| R2-2004192 | Allowing PDCP version change without handover | Ericsson, Intel Corporation |
| R2-2004246 | Avoiding security risk for RLC AM bearers during termination point change | Nokia, Nokia Shanghai Bell, Deutsche Telekom |
| R2-2004247 | Avoiding security risk for RLC AM bearers during termination point change | Nokia, Nokia Shanghai Bell, Deutsche Telekom |
| R2-2004262 | UE measurement capability requirements for NR | Google Inc. |
| R2-2004263 | UE measurement capability requirements for NR | Google Inc. |
| R2-2004265 | LS on Calculation of ShortResumeMAC-I | RAN2 |
| 5.4.3 | UE capabilities and Capability Coordination | |
| R2-2002505 | LS on XDD-FRX Differentiation (R1-1913579; contact: Qualcomm) | RAN1 |
| R2-2002509 | Reply LS on default codebook parameters (R1-2001307; contact: Nokia) | RAN1 |
| R2-2002552 | Reply LS on default codebook parameters (R1-2001307; contact: Nokia) | RAN1 |
| R2-2002571 | Corrections on the number of DRBs | Qualcomm Incorporated |
| R2-2002572 | Corrections on the number of DRBs | Qualcomm Incorporated |
| R2-2002573 | xDD FRx split capabilities. | Qualcomm Incorporated |
| R2-2002574 | Correction on UE capability signalling for simultaneous SRS antenna and carrier switching | Qualcomm Incorporated |
| R2-2002578 | Signalling of NR-DC only band combination | Qualcomm Incorporated |
| R2-2002579 | Clarification on supported NR-DC cell grouping | Qualcomm Incorporated |
| R2-2002635 | Correction of Band Parameter (v1540) | OPPO, ZTE Corporation, Sanechips |
| R2-2002636 | Correction of Band Parameter (v1540) | OPPO, ZTE Corporation, Sanechips |
| R2-2002637 | Correction of Band Parameter (v1600) | OPPO, ZTE Corporation, Sanechips |
| R2-2002654 | Discussion on XDD FRX difference | OPPO |
| R2-2002655 | 38306_CRyyyy_(REL-15)_Correct on XDD FRX difference | OPPO |
| R2-2002678 | Corrections on bwp-WithoutRestriction | OPPO |
| R2-2002694 | Clarification on BandParameters of BandCombination | ZTE Corporation, Sanechips, OPPO |
| R2-2002695 | Corrections on BandParameters of BandCombination | ZTE Corporation, Sanechips, OPPO |
| R2-2002696 | CR on unnecessary FRx differentiation | ZTE Corporation, Sanechips |
| R2-2002724 | Correction to need code for capabilityRequestFilterCommon | MediaTek Inc. |
| R2-2002802 | Handling of Fallbacks for Contiguous and Non-contiguous CA in FR2 | Apple, Nokia, Nokia Shanghai Bell, Intel, InterDigital, Xiaomi Communications, Spreadtrum Communications, CMCC, Panasonic |
| R2-2002803 | FR2 CA fallback | Apple, Nokia, Nokia Shanghai Bell, Intel, InterDigital, Xiaomi Communications, Spreadtrum Communications, CMCC, Panasonic |
| R2-2002804 | FR2 CA fallback | Apple, Nokia, Nokia Shanghai Bell, Intel, InterDigital, Xiaomi Communications, Spreadtrum Communications, CMCC, Panasonic |
| R2-2002989 | TS 38.331 Dummifying bandwidth class F | Nokia, Nokia Shanghai Bell |
| R2-2002990 | TS 38.306 Clarifying consequences if not supported | Nokia, Nokia Shanghai Bell, NTT Docomo Inc. |
| R2-2003269 | Signaling for XDD-FRX differentiation | Ericsson |
| R2-2003270 | Signaling for XDD-FRX differentiation (38.331) | Ericsson |
| R2-2003271 | Signaling for XDD-FRX differentiation (38.331) | Ericsson |
| R2-2003272 | Signaling for XDD-FRX differentiation (38.306) | Ericsson |
| R2-2003273 | Signaling for XDD-FRX differentiation (38.306) | Ericsson |
| R2-2003274 | Ambiguity in fr1-fr2-Add-UE-NR-Capabilities parameter | Ericsson, NTT Docomo |
| R2-2003275 | Ambiguity in fr1-fr2-Add-UE-NR-Capabilities parameter | Ericsson, NTT Docomo |
| R2-2003280 | Missing "Optional features without UE radio access capability parameters" | Ericsson |
| R2-2003281 | Missing "Optional features without UE radio access capability parameters" | Ericsson |
| R2-2003306 | Undefined band combinations in UECapabilityInformation | Ericsson |
| R2-2003307 | Bands in supportedBandListNR | Ericsson |
| R2-2003308 | Email discussion report: Post109e#24][NR15] Clarification of capabilities with NR-DC and NE-DC | Ericsson |
| R2-2003443 | [Post109e#25][NR15] SRS Capability report for SRS only Scell summary | Huawei, HiSilicon |
| R2-2003444 | SRS Capability report for SRS only Scell | Huawei, HiSilicon |
| R2-2003445 | SRS Capability report for SRS only Scell | Huawei, HiSilicon |
| R2-2003454 | Discussion on capabilities with XDD-FRX differentiations | Huawei, HiSilicon |
| R2-2003455 | Draft LS on capabilities with XDD-FRX differentiations | Huawei, HiSilicon |
| R2-2003456 | Discussion on the capability of Basic CSI feedback (2-32) | Huawei, HiSilicon, Orange, Telecom Italia S.p.A., Vodafone, CMCC, China Unicom, China Telecom |
| R2-2003457 | CR on the capability of Basic CSI feedback (2-23) | Huawei, HiSilicon, Orange, Telecom Italia S.p.A., Vodafone, CMCC, China Unicom, China Telecom |
| R2-2003458 | CR on the capability of Basic CSI feedback (2-23) | Huawei, HiSilicon, Orange, Telecom Italia S.p.A., Vodafone, CMCC, China Unicom, China Telecom |
| R2-2003459 | Correction on default Power class for FR2 | Huawei, HiSilicon |
| R2-2003460 | Correction on default Power class for FR2 | Huawei, HiSilicon |
| R2-2003461 | Correction to the serving cell number for ENDC power class | Huawei, HiSilicon |
| R2-2003462 | Correction to the serving cell number for ENDC power class | Huawei, HiSilicon |
| R2-2003463 | Correction to RequestedCapabilityCommon | Huawei, HiSilicon |
| R2-2003464 | Correction to RequestedCapabilityCommon | Huawei, HiSilicon |
| R2-2003541 | Correction on bwp-SwitchingDelay | Huawei, HiSilicon |
| R2-2003542 | Correction on bwp-SwitchingDelay | Huawei, HiSilicon |
| R2-2003737 | Fallback band combinations | Ericsson, AT&T, T-Mobile, Vodafone, Deutsche Telekom, Telecom Italia S.p.A, NTT DOCOMO INC. |
| R2-2003750 | Discussion on XDD-FRX differentiation in UE capability | ZTE Corporation, Sanechips |
| R2-2003751 | CR to 38.306 on XDD-FRX differentiation in UE capability | ZTE Corporation, Sanechips |
| R2-2003752 | CR to 38.331 on XDD-FRX differentiation in UE capability | ZTE Corporation, Sanechips |
| R2-2003764 | CR on the capability of Basic CSI feedback (2-32) | Huawei, HiSilicon, Orange, Telecom Italia S.p.A., Vodafone, CMCC, China Unicom, China Telecom |
| R2-2003765 | CR on the capability of Basic CSI feedback (2-32) | Huawei, HiSilicon, Orange, Telecom Italia S.p.A., Vodafone, CMCC, China Unicom, China Telecom |
| R2-2003816 | CR on the capability of Basic CSI feedback (2-32) | Huawei, HiSilicon, Orange, Telecom Italia S.p.A., Vodafone, CMCC, China Unicom, China Telecom, Ericsson |
| R2-2003817 | CR on the capability of Basic CSI feedback (2-32) | Huawei, HiSilicon, Orange, Telecom Italia S.p.A., Vodafone, CMCC, China Unicom, China Telecom, Ericsson |
| R2-2003832 | Fallback band combinations | Ericsson, AT&T, T-Mobile, Vodafone, Deutsche Telekom, Telecom Italia S.p.A, NTT DOCOMO INC., Turkcell, BT, China Telecom, Reliance Jio, Telstra, LG Uplus, Orange, Dish Network |
| R2-2004117 | Summary for offline [013][NR15] UE Cap Codebook parameters | Huawei, Nokia |
| R2-2004163 | Reply LS on the applicability of UE capabilities for NE-DC (R1-2002792; contact: ZTE) | RAN1 |
| R2-2004176 | Reply LS on Handling of Fallbacks for combined contiguous and non-contiguous CA or DC configurations in FR2 | MediaTek Inc |
| R2-2004197 | SRS Capability report for SRS only Scell | Huawei, HiSilicon |
| R2-2004198 | SRS Capability report for SRS only Scell | Huawei, HiSilicon |
| R2-2004199 | SRS Capability report for SRS only Scell | Huawei, HiSilicon |
| R2-2004200 | SRS Capability report for SRS only Scell | Huawei, HiSilicon |
| R2-2004206 | Corrections on the number of DRBs | Qualcomm Incorporated |
| R2-2004207 | Corrections on the number of DRBs | Qualcomm Incorporated |
| R2-2004213 | CR on the capability of Basic CSI feedback (2-32) | Huawei, HiSilicon, Orange, Telecom Italia S.p.A., Vodafone, CMCC, China Unicom, China Telecom, Ericsson |
| R2-2004267 | Reply LS on Handling of Fallbacks for combined contiguous and non-contiguous CA or DC configurations in FR2 | RAN2 |
| 5.4.4 | Idle/inactive mode procedures | |
| R2-2003339 | Corrections to cell barred handling | Huawei, HiSilicon |
| R2-2003340 | Corrections to cell barred handling | Huawei, HiSilicon |
| R2-2003773 | Corrections to cell barred handling | Huawei, HiSilicon |
| 6.0.1 | RRC ASN.1 review | |
| R2-2003078 | [E008] On adding LBTFailure as RLF cause | Ericsson |
| R2-2003079 | [E008] On adding LBTFailure as SCG Failure cause | Ericsson |
| R2-2003094 | [E051] On excluding the 2 step RA related RAReport | Ericsson |
| R2-2003230 | ASN.1/ general protocol issues on UE power saving (S406, S407, S408) | Samsung Telecommunications |
| R2-2003309 | TS 38.331 Rel-16 ASN.1 review file, phase 1 | Ericsson |
| R2-2003310 | RIL list TS 38.331 Rel-16 ASN.1 review file, phase 1 | Ericsson |
| R2-2003311 | [H155] Change the type of reference time from integer to bitstring | Huawei, HiSilicon |
| R2-2003325 | [I630, I631, I632, I633] General discussion on Rel-16 ASN.1 related issues | Intel Corporation |
| R2-2003388 | ASN.1/ general protocol issues on UE power saving (S406, S407, S408) | Samsung Telecommunications |
| R2-2003412 | [S051] Correction to NR-U and IIoT merger for harq-ProcID-offset | Ericsson |
| R2-2003413 | [S051] Correction to NR-U and IIoT merger for harq-ProcID-offset | Ericsson |
| R2-2003583 | [H016][H019][MDTSON] Discussion on the meaning of reportInterval for UL delay measurements | Huawei, HiSilicon |
| R2-2003584 | [H017][MDTSON] Discussion on the field CGI-InfoEUTRALogging | Huawei, HiSilicon |
| R2-2003585 | [H018][MDTSON] Discussion on PLMN id in the UE variable on CEF report | Huawei, HiSilicon |
| R2-2003617 | Introduction of the new L1 parameters for eURLLC [H042][H044][H050] | Huawei, HiSilicon |
| R2-2003626 | [H003] Discussion on time domain resource allocation in multiple R16 topics | Huawei, HiSilicon |
| R2-2003627 | [H004] Discuission on the ASN.1 of inter-dependent field values | Huawei, HiSilicon |
| R2-2003628 | [H005] Discussion on delta signaling without AddModList | Huawei, HiSilicon |
| R2-2003629 | [H002] Discussion on the use of SEQUENCE of SEQUENCE and CHOICE | Huawei, HiSilicon |
| R2-2003630 | [H072] DraftCR for the overall organization of signalling for 2stepRACH | Huawei, HiSilicon |
| R2-2003631 | [H076-079] DraftCR for RACH-ConfigCommonTwoStepRA | Huawei, HiSilicon |
| R2-2003632 | [H062][H065] DraftCR for slotOffset for aperiodic SRS | Huawei, HiSilicon |
| R2-2003633 | [H063][H066][H070][H071] DraftCR for the configuration of spatial relation for SRS with SSB | Huawei, HiSilicon |
| R2-2003634 | [H207][H208][H209][H211][H218] DraftCR for on-demand SI request for positioning in RRC_CONNECTED | Huawei, HiSilicon |
| R2-2003635 | [H221] DraftCR for DedicatedSIB-Request | Huawei, HiSilicon |
| R2-2003636 | [H215][H216][H217][H219] DraftCR for Actions upon reception of the SIB1 | Huawei, HiSilicon |
| R2-2003637 | [H222] DraftCR for on-demand SI request for positioning in RRC_CONNECTED | Huawei, HiSilicon |
| R2-2003638 | [H226] TP for the search space group switching for CSS | Huawei, HiSilicon |
| R2-2003639 | [H227] TP for the decription for CG configuration | Huawei, HiSilicon |
| R2-2003654 | [M105][DCCA][MDT] Discussion on MeasResult2EUTRA | MediaTek Inc. |
| R2-2003788 | [E032] Correction to UE response procedure for idle measurements | Ericsson |
| R2-2003820 | General ASN.1 issues for 36.331 Rel-16 (S007) | Samsung R&D Institute UK |
| R2-2003869 | Rel-16 ASN.1 review plan, phase 2 | Ericsson, Samsung |
| R2-2004231 | Summary of [AT109bis-e][070][NR RIL] DiscMail7+DiscMail9 | vivo |
| R2-2004232 | DraftCR for [AT109bis-e][070][NR RIL] DiscMail7+DiscMail9 | vivo |
| R2-2004235 | RRC CR Handling | Chairman |
| R2-2004244 | [AT109bis-e][065][NR RIL] DiscMail1 | Ericsson |
| R2-2004271 | LS on conflicting configurations | RAN2 |
| R2-2004272 | Summary of [AT109bis-e][070][NR RIL] DiscMail7+DiscMail9 | vivo |
| R2-2004273 | DraftCR for [AT109bis-e][070][NR RIL] DiscMail7+DiscMail9 | vivo |
| R2-2004274 | [AT109bis-e][068][NR RIL] DiscMail4 (Huawei) | Huawei, HiSilicon |
| R2-2004275 | Email discussion report: [AT109bis-e][072][NR RIL] DiscMail11 + DiscMail12 | Ericsson |
| R2-2004277 | The summary of [AT109bis-e][069][NR RIL] DiscMail5 and DiscMail6 (ZTE) | ZTE |
| R2-2004278 | Report from email discussion [AT109bis-e][071][NR RIL] DiscMail10 | Lenovo |
| 6.0.2 | Feature List and UE capabilities | |
| R2-2003373 | UE capabilities for RAN1 feature list | Intel Corporation, NTT DOCOMO, INC. |
| R2-2003374 | UE capabilities for RAN1 feature list | Intel Corporation, NTT DOCOMO, INC. |
| R2-2003375 | Update for Rel-16 UE capabilities | Intel Corporation, NTT DOCOMO, INC. |
| R2-2003447 | Discussion on the way of capturing Rel-16 UE capabilities | Huawei, HiSilicon |
| R2-2004202 | Rel-16 UE capability Handling Discussion | Intel Corporation |
| 6.0.3 | Other | |
| R2-2002512 | LS on RAN1 input to Rel-16 TS 38.300 on V2X, Positioning and MR-DC (R1-2001356; contact: Nokia) | RAN1 |
| R2-2003024 | Usage of eLCID field | MediaTek Inc. |
| R2-2003201 | [E038] Triggering of fast MCG recovery upon T312 expiry | Ericsson |
| R2-2003202 | [E050] Support of SIB9 for on-demand SIB procedure in CONNECTED | Ericsson |
| R2-2003714 | [H230 ] Extension of a single Need M item to a list of this item | Huawei, HiSilicon |
| R2-2003715 | [H231] Extending the number of entries of a list not using ToAddMod list | Huawei, HiSilicon |
| R2-2003716 | [H232] Extension to the contents of items of a list using ToAddMostList in absence of extension markers | Huawei, HiSilicon |
| R2-2003717 | [H233] Moving parameters used by RRCConnectionReconfiguration and RRCConnectionResume to IEs | Huawei, HiSilicon |
| R2-2004172 | Summary of offline-060 MAC eLCID and RACH stopping | LG Electronics Inc., MediaTek |
| R2-2004216 | 38321 CR Clarification on eLCID | LG Electronics Inc., MediaTek |
| 6.1.1 | Organisational | |
| R2-2002727 | IAB workplan update | Qualcomm Incorporated (Rapporteur) |
| R2-2003868 | LS on UAC applicability to IABs | RAN2 |
| R2-2003941 | LS on UAC applicability to IABs | RAN2 |
| R2-2004169 | Reply LS on T_delta in IAB (R1-2002931; contact: ZTE) | RAN1 |
| 6.1.2 | Stage-2 Corrections | |
| R2-2002728 | Notation of IAB terminology | Qualcomm Incorporated (Rapporteur) |
| R2-2003014 | Miscellaneous correction to 37.340 for IAB | Huawei, HiSilicon |
| R2-2003178 | F1AP over LTE leg signalling correction to 37.340 | Nokia, Nokia Shanghai Bell |
| R2-2003300 | On Multi-connectivity for IAB | Ericsson |
| R2-2004132 | [AT 109bis-e][018][IAB] IAB terminology and other issues | Qualcomm (Rapporteur) |
| R2-2004133 | CR to 38.300 on Integrated Access and Backhaul for NR | Qualcomm (Rapporteur) |
| R2-2004151 | Miscellaneous correction to 37.340 for IAB | Huawei, HiSilicon |
| 6.1.3 | BAP Open Issues and Corrections | |
| R2-2002851 | Further consideration on bearer mapping | ZTE, Sanechips |
| R2-2002889 | Remaining issues of DL HbH FC | vivo |
| R2-2003002 | TP on clarifying a condition and aligning a terminology in BAP specification | LG Electronics Inc. |
| R2-2003011 | Miscellaneous corrections to 38.340 for IAB | Huawei, HiSilicon |
| R2-2003015 | The bearer mapping configuration on the backup link in RLF | Huawei, HiSilicon |
| R2-2003176 | Corrections to BAP | Nokia, Nokia Shanghai Bell |
| R2-2003438 | On Release of BAP Entities | CATT |
| R2-2003561 | Summary of 6.1.3 for BAP open issues and corrections | Huawei, HiSilicon |
| R2-2003725 | IP address assignment for IAB node DU on failure handling | Samsung R&D Institute UK |
| R2-2004152 | Summary of email discussion [AT109bis-e][019][IAB] BAP | Huawei |
| R2-2004153 | Miscellaneous corrections to 38.340 for IAB | Huawei, HiSilicon |
| 6.1.4 | User plane Open Issues and Corrections | |
| R2-2002679 | On interpretation and use of the Guard Symbols MAC CE | Samsung Electronics GmbH |
| R2-2002680 | Open issues with IAB LCID space extension | Samsung Electronics GmbH |
| R2-2002690 | Finalising Rel-16 MAC design (IAB-related open issues) | Samsung Electronics GmbH |
| R2-2002691 | CR (IAB MAC - rapporteur corrections and clarifications) | Samsung Electronics GmbH |
| R2-2002715 | Introducing a section for handling of Tdelta MAC CE | Samsung Electronics GmbH |
| R2-2002716 | Summary of IAB User Plane open issues and corrections | Samsung Electronics GmbH |
| R2-2002852 | Discussion on IAB User plane aspects | ZTE, Sanechips |
| R2-2002890 | Renamed to be: remaining issues of preemtpive BSR | vivo |
| R2-2002999 | Determining a cell to apply a Guard Symbols MAC CE | LG Electronics Inc. |
| R2-2003000 | Consideration on LCID set for IAB MAC CE and reserved LCID values | LG Electronics Inc. |
| R2-2003001 | TP for remaining issues on Guard Symbols MAC CE and LCID extension | LG Electronics Inc. |
| R2-2003016 | Remaining issues of Guard Symbols MAC CE | Huawei, HiSilicon |
| R2-2003017 | Clarification on the RACH configuration used in MAC procedure for IAB | Huawei, HiSilicon |
| R2-2003018 | Clarification of BSR and Pre-emptive BSR | Huawei, HiSilicon |
| R2-2003019 | Discussion on the SR cancelation for pre-BSR and LCID values for IAB | Huawei, HiSilicon |
| R2-2003048 | Cell information in Guard symbols MAC CE | Nokia, Nokia Shanghai Bell |
| R2-2003049 | Handling of IAB specific MAC CEs | Nokia, Nokia Shanghai Bell |
| R2-2003098 | PDCP duplication in IAB DC | Lenovo, Motorola Mobility |
| R2-2003359 | Change LCID to eLCID for IAB MAC CEs | Ericsson |
| R2-2003644 | Issue of SR triggered by Pre-emptive BSR | ASUSTeK |
| R2-2003720 | Remaining issues for IAB MAC | Futurewei |
| R2-2003826 | Summary of IAB User Plane open issues and corrections | Samsung Electronics GmbH |
| R2-2003829 | Summary of IAB User Plane open issues and corrections | Samsung Electronics GmbH |
| R2-2003830 | IAB MAC - rapporteur corrections and clarifications | Samsung |
| R2-2003831 | Introducing a section for handling of Tdelta MAC CE | Samsung Electronics GmbH |
| R2-2004126 | IAB MAC - rapporteur corrections and clarifications | Samsung |
| R2-2004127 | LS to RAN1 on Guard Symbols in IAB | RAN2 |
| R2-2004128 | Remaining issues from IAB User Plane | Samsung |
| 6.1.5 | RRC Open Issues and corrections | |
| R2-2002600 | Considerations on BAP entity release | KDDI Corporation |
| R2-2002853 | Remaining issues for F1-C over LTE | ZTE, Sanechips |
| R2-2002854 | Misellaneous RRC issues for IAB | ZTE, Sanechips |
| R2-2003020 | ASN.1 issues related to L1 parameters for IAB | Huawei, HiSilicon |
| R2-2003021 | Draft LS to RAN1 on IAB L1 parameters | Huawei, HiSilicon |
| R2-2003297 | Report on email discussion [Post109e][035][IAB] RRC open issues | Ericsson |
| R2-2003298 | Correction for TS 38.331 Related to IAB WI | Ericsson |
| R2-2003299 | Correction for TS 36.331 Related to IAB WI | Ericsson |
| R2-2003301 | Allowing an IAB configuration without DRB | Ericsson |
| R2-2003595 | On the need of a new cause in SCG Failure Information | LG Electronics France |
| R2-2003596 | No need to support RRC_INACTIVE for IAB-MT | LG Electronics France |
| R2-2003598 | On RRC connection without DRB | LG Electronics France |
| R2-2003726 | SCGFailureInformation procedure in IAB RLF handling | Samsung R&D Institute UK |
| R2-2003728 | [S020],[S021] SMTC occasion calculation for smtc3 for IAB-MT | Samsung R&D Institute UK |
| R2-2003742 | [S020] Conditional presence on smtc3 in IAB | Samsung R&D Institute UK |
| R2-2003743 | [S021] Clarification on smtc3 operation in IAB | Samsung R&D Institute UK |
| R2-2004125 | Correction for TS 38.331 Related to IAB WI | Ericsson |
| R2-2004243 | Correction for TS 38.331 for IAB WI | Ericsson |
| R2-2004287 | Correction for TS 38.331 for IAB WI | Ericsson |
| 6.1.6 | RLF Handling Open Issues | |
| R2-2002729 | Report email discussion [Post109e#36][IAB] RLF Handling Open Issues | Qualcomm Incorporated |
| R2-2002855 | Discussion on IAB BH RLF handling | ZTE, Sanechips |
| R2-2002991 | Discussion on IAB BH RLF handling | NEC |
| R2-2003099 | Fast MCG link recovery for IAB DC case | Lenovo, Motorola Mobility |
| R2-2003236 | Remaining details for Backhaul RLF Handling | Futurewei |
| R2-2003302 | Further details on Backhaul link RLF Notification Types to Downstream Node(s) | Ericsson |
| R2-2003304 | Backhaul RLC Channel Remapping for IAB node(s) | Ericsson |
| R2-2003314 | Possible issues on Backhaul RLF handling | Kyocera |
| R2-2003775 | Report email discussion [Post109e#36][IAB] RLF Handling Open Issues | Qualcomm Incorporated |
| R2-2003813 | Report email discussion [Post109e#36][IAB] RLF Handling Open Issues | Qualcomm Incorporated |
| 6.1.7 | IP address allocation Open Issues | |
| R2-2002522 | LS on the inter donor DU re-routing and source IP configuration (R3-201418; contact: Huawei)) | RAN3 |
| R2-2002523 | LS on IP address management in IAB network (R3-201420; contact: Samsung) | RAN3 |
| R2-2002672 | Report on email discussion Post109e_26 IAB IP address allocation (Samsung) | Samsung Electronics GmbH |
| R2-2002856 | Remaining issues of IP address allocation | ZTE, Sanechips |
| R2-2003180 | IP address request in NSA and SA | Nokia, Nokia Shanghai Bell |
| R2-2003303 | IP Address Assignment for IAB Node(s) | Ericsson |
| R2-2003525 | IP address allocation for IAB-nodes | Futurewei |
| R2-2004142 | Way forward on IP address allocation for IAB nodes | Samsung |
| 6.1.8 | UE capabilities | |
| R2-2002717 | Optional Rel-15 UE Features for IAB-MTs | AT&T |
| R2-2002730 | Optionality of mandatory Rel-15 features for IAB-MT | Qualcomm Incorporated |
| R2-2002857 | Rel-15 mandatory UE features for Rel-16 IAB-MT | ZTE, Sanechips |
| R2-2002858 | Discussion on channel bandwidth for Rel-16 IAB-MT | ZTE, Sanechips |
| R2-2002891 | IAB-MT Capability of Rel-15 features | vivo |
| R2-2003022 | Capturing IAB capability | Huawei, HiSilicon |
| R2-2003177 | IAB-MT features list and capabilities | Nokia, Nokia Shanghai Bell |
| R2-2003323 | Mandatory/optional features for IAB-MT | Intel Corporation |
| R2-2003360 | Rel-15 capabilities to be supported by IAB-MT | Ericsson |
| R2-2003361 | Capability signalling for IAB | Ericsson |
| R2-2003439 | Views on IAB MT Capability | CATT |
| R2-2003597 | Capabilities of IAB MTs | LG Electronics France |
| R2-2003727 | Considering the optionality of Rel-15 UE features for IAB-MT use | Samsung R&D Institute UK |
| R2-2003794 | Summary of 6.1.8 UE capabilities for IAB-MT | Nokia, Nokia Shanghai Bell |
| 6.1.9 | Other Corrections | |
| R2-2002664 | PWS information handling in IAB | Sony |
| R2-2002814 | Better cell selection for IAB Nodes | Apple |
| R2-2003012 | Miscellaneous corrections to 38.304 for IAB | Huawei, HiSilicon |
| R2-2003013 | Miscellaneous corrections to 36.304 for IAB | Huawei, HiSilicon |
| R2-2003179 | Cell re-selection handling for IAB-MT | Nokia, Nokia Shanghai Bell |
| R2-2003346 | IAB support in NPN deployment | Kyocera |
| R2-2004154 | Summary of [AT109bis-e][024] 3X.304 CRs and IAB supporting in NPN | Huawei |
| R2-2004155 | Miscellaneous corrections to 38.304 for IAB | Huawei, HiSilicon |
| R2-2004156 | Miscellaneous corrections to 36.304 for IAB | Huawei, HiSilicon |
| R2-2004225 | Miscellaneous corrections to 38.304 for IAB | Huawei, HiSilicon |
| R2-2004226 | Miscellaneous corrections to 36.304 for IAB | Huawei, HiSilicon |
| R2-2004227 | Corrections to 38.331 for supporting IAB in NPN | Huawei, HiSilicon |
| R2-2004228 | Corrections to 38.304 for supporting IAB in NPN | Huawei, HiSilicon |
| R2-2004229 | Draft LS on IAB supporting in NPN deployment | Huawei, HiSilicon |
| R2-2004280 | Corrections to 38.331 for supporting IAB in NPN | Huawei, HiSilicon, Kyocera |
| R2-2004281 | Corrections to 38.304 for supporting IAB in NPN | Huawei, HiSilicon, Kyocera |
| R2-2004282 | LS on IAB supporting in NPN deployment | RAN2 |
| 6.2.1 | General | |
| R2-2002506 | LS to RAN2 on NR-U related changes for 38.300 running CR (R1-2001300; contact: Qualcomm) | RAN1 |
| R2-2002513 | LS on SSB index and candidate SSB index for NR-U (R1-2001357; contact: Samsung, Charter Communications) | RAN1 |
| R2-2002514 | LS on NR-U enhancements to initial access procedures (R1-2001375; contact: Charter Communications) | RAN1 |
| R2-2002516 | Reply LS on consistent Uplink LBT failure detection mechanism (R1-2001397; contact: Nokia) | RAN1 |
| R2-2002530 | LS on UL LBT failure recovery for the target cell (R4-2002282; contact: Ericsson) | RAN4 |
| R2-2002584 | Running CR to 38.306 on Introducing UE Capability for NR Shared Spectrum | vivo |
| R2-2002586 | Running CR to 38.306 on Introducing UE Capability for NR Shared Spectrum | vivo |
| R2-2002844 | Report of Post109e#40][NR-U] UE capabilities | Qualcomm Incorporated |
| R2-2003008 | Reply LS on consistent Uplink LBT failure detection mechanism | Nokia |
| R2-2003965 | Reply LS on consistent Uplink LBT failure detection mechanism | Nokia |
| R2-2003971 | Reply LS on consistent Uplink LBT failure detection mechanism | RAN2 |
| R2-2004174 | LS on intra-cell guard band configuration for NR-U (R1-2002908; contact: LGE) | RAN1 |
| 6.2.2 | User plane | |
| R2-2002582 | Clarification on the LBT Failure Indication | vivo |
| R2-2002583 | Discussion on the UE Processing Time for Autonomous Retransmission | vivo |
| R2-2002613 | Clash between NR-U and IIoT for the configured grant | Samsung |
| R2-2002614 | Prioritization between initial TX and re-TX on CG in NR-U | Samsung |
| R2-2002837 | Discussion incoming RAN1 LS on LBT failure indication | OPPO |
| R2-2002848 | Remaining critical issues for LBT failures | Qualcomm Incorporated |
| R2-2002931 | Stopping ongoing Random Access procedure | LG Electronics Inc. |
| R2-2003004 | Remaining issue on 2-step random access in NR-U | Huawei, HiSilicon |
| R2-2003005 | Discussion on the MAC CE for NR-U | Huawei, HiSilicon |
| R2-2003006 | Discussion on PDCCH group switching for NR-U | Huawei, HiSilicon |
| R2-2003031 | Flushing HARQ buffer of the pending HARQ process in NR-U | LG Electronics Polska |
| R2-2003050 | Draft CR on LBT failure handling in MAC | Nokia, Nokia Shanghai Bell |
| R2-2003409 | Corrections of NR-U in 38.321 | Ericsson |
| R2-2003410 | UEs not supporting gap-less msgA transmission | Ericsson |
| R2-2003411 | Post109e#39 NR-U MAC open issues | Ericsson |
| R2-2003498 | MsgA PUSCH LBT failure impact | CMCC |
| R2-2003875 | Corrections of NR operating with shared spectrum channel access in 38.321 | Ericsson |
| R2-2003951 | Post109e#39 NR-U MAC open issues | Ericsson |
| R2-2003952 | Summary of NR-U User plane | InterDigital |
| R2-2003966 | [Draft] reply LS on UL LBT failure recovery for the target cell | InterDigital |
| R2-2003972 | [Draft] reply LS on UL LBT failure recovery for the target cell | InterDigital |
| R2-2003973 | Reply LS on UL LBT failure recovery for the target cell | RAN2 |
| 6.2.3 | Control plane | |
| R2-2002615 | Applicability of NR-U features to licensed carrier | Samsung |
| R2-2002719 | On Q-values for Measurements in NR-U | Mediatek Inc. |
| R2-2002843 | Report of [Post109e#38][NR-U] RRC open issues | Qualcomm Incorporated |
| R2-2002845 | E-UTRAN and NR-U interworking | Qualcomm Incorporated |
| R2-2002846 | NR-U RRC Open Issues List | Qualcomm Incorporated |
| R2-2002847 | Miscellaneous corrections for NR-U | Qualcomm Incorporated |
| R2-2002910 | Description on Short Message in TS38.331 | LG Electronics Inc. |
| R2-2002966 | Addressing RAN1 and RAN4 questions on LBT failure configuration | ZTE Corporation, Sanechips |
| R2-2002967 | Draft-Reply LS on consistent UL LBT failure detection mechanism | ZTE Corporation, Sanechips |
| R2-2002968 | Draft-Reply LS on LS on UL LBT failure recovery for the target cell | ZTE Corporation, Sanechips |
| R2-2003041 | Remaining control plane issues | Ericsson |
| R2-2003407 | LS reply to RAN4 on UL LBT failure recovery for the target cell | Ericsson |
| R2-2003408 | UL LBT failure recovery for target cell | Ericsson |
| R2-2003414 | Mobility to NR operating with shared spectrum access | Qualcomm Incorporated |
| R2-2003878 | Miscellaneous corrections for NR-U | Qualcomm Incorporated (Rapporteur) |
| R2-2003953 | [AT109bis-e][501][NR-U] CP Open and ASN.1 Issues (Qualcomm) | Qualcomm Incorporated |
| R2-2004279 | Mobility to NR operating with shared spectrum access | Qualcomm Incorporated |
| 6.4.1 | General | |
| R2-2002507 | Reply LS on NR V2X resource pool configuration and selection (R1-2001304; contact: vivo) | RAN1 |
| R2-2002518 | LS on sidelink HARQ (R1-2001426; contact: LGE) | RAN1 |
| R2-2002541 | LS reply to RAN WG2 LS on NR V2X Security issue and PDCP SN size (S3-200478; contact: CATT) | SA3 |
| R2-2002563 | (draft)LS response to SA3 on NR V2X security issue | ZTE Corporation, Sanechips |
| R2-2002662 | Minor Correction in TS38.300 on SL physical layer measurements | Nokia, Nokia Shanghai Bell |
| R2-2003513 | [DRAFT] LS response to SA3 on the security related issues for NR SL | Huawei, HiSilicon |
| R2-2003519 | RRC Open Issue List for 5G V2X with NR SL | Huawei (Rapporteur) |
| R2-2003672 | Draft LS response to RAN1 on sidelink HARQ | Huawei, Hisilicon |
| R2-2003818 | [DRAFT] LS to RAN1 on configurations of L1 parameters in RRC | Huawei, HiSilicon |
| R2-2004162 | LS on the 3GPP work on the NR sidelink (S-200078; contact: VolksWagen) | 5GAA WG4 |
| R2-2004168 | LS on LTE V2X capabilities in NR V2X (R1-2002930; contact: Huawei) | RAN1 |
| R2-2004179 | LS reply to RAN WG2 LS on NR V2X Security issues (S3-200820; contact: CATT) | SA3 |
| 6.4.2 | Control plane | |
| R2-2002652 | 38331_CRyyyy_(REL-16)_Correct to fix SIB12 size issue for NR V2X | OPPO |
| R2-2004076 | Correct to fix SIB12 size issue for NR V2X | OPPO |
| 6.4.2.1 | RRC | |
| R2-2002564 | Discussion on NR V2X remaining RRC issues | ZTE Corporation, Sanechips |
| R2-2002567 | (draft)CR on TS 38.331 for NR V2X on miscellaneous issues | ZTE Corporation, Sanechips |
| R2-2002621 | Discussion on RRC open issues [N001,N002,N005] | OPPO |
| R2-2002622 | Draft-CR on RRC open issues of 38.331 [N001,N002,N005] | OPPO |
| R2-2002651 | Open issues on system information | OPPO |
| R2-2002653 | 36331_CRyyyy_(REL-16)_ Correct on SIB28 message for NR V2X | OPPO |
| R2-2002722 | Configuration failure handling on PC5 | MediaTek Inc. |
| R2-2002807 | Remaining issues on PC5-RRC procedures | Apple |
| R2-2002821 | Triggering condition for sidelink RSRP reporting | MediaTek Inc. |
| R2-2002828 | Further Discussion on RRC Remaining Issues | CATT |
| R2-2002850 | Left issue on RRC for NR V2X | LG Electronics France |
| R2-2002918 | Summary of [Post109e#54][V2X] RRC Open Issues | Huawei (Rapporteur) |
| R2-2002919 | Discussion on remaining RRC Open issues for 5G V2X with NR SL | Huawei, HiSilicon |
| R2-2002920 | Draft CR to TS 38.331 on the remaining RRC Open issues for 5G V2X with NR SL | Huawei, HiSilicon |
| R2-2002921 | Draft CR to TS 38.321 on the remaining RRC Open issues for 5G V2X with NR SL | Huawei, HiSilicon |
| R2-2003096 | RRC remaining issues for NR V2X | Lenovo, Motorola Mobility |
| R2-2003114 | SL RSRP report triggering | Ericsson |
| R2-2003293 | Open HARQ Issues | Fraunhofer HHI, Fraunhofer IIS |
| R2-2003295 | Reporting of Sensing Result for Mode 1 UEs | Fraunhofer HHI, Fraunhofer IIS, AT&T, Deutsche Telekom |
| R2-2003312 | Remaining issues on RRC for NR V2X | Nokia, Nokia Shanghai Bell |
| R2-2003338 | Draft CR 38.331 Remaining issues on RRC for V2X Sidelink | Nokia, Nokia Shanghai Bell |
| R2-2003347 | RLF handling under multiple PC5-RRC connections | Kyocera |
| R2-2003514 | Corrections on V2X functionalities in TS 36.331 | Huawei, HiSilicon |
| R2-2003520 | Summary document for AI 6.4.2.1 - RRC aspects | Huawei, HiSilicon |
| R2-2003528 | Remaining issues for Sidelink AS Reconfiguration | Qualcomm Finland RFFE Oy |
| R2-2003536 | Draft CR to 38.331 on AS reconfiguration failure | Qualcomm Finland RFFE Oy |
| R2-2003559 | Miscellaneous corrections to 38.331 for V2X | Huawei, HiSilicon |
| R2-2003645 | Remaining issues on RRC specification | ASUSTeK |
| R2-2003646 | Clarification on UE behaviour for sidelink RoHC configuration | ASUSTeK |
| R2-2003722 | RRC connection initiation trigger for SLRB configuration handling | Samsung Electronics Co., Ltd |
| R2-2003759 | CR on new RRC connection initiation trigger in V2X | Samsung Electronics Co., Ltd |
| R2-2004071 | Summary of offline discussion [AT109bis-e][701][V2X] RRC open issues and ASN.1 class2/3 issues | Huawei (Rapporteur) |
| R2-2004072 | Miscellaneous corrections to 38.331 for V2X | Huawei, HiSilicon |
| R2-2004073 | Corrections on V2X functionalities in TS 36.331 | Huawei, HiSilicon |
| R2-2004074 | Draft LS to RAN1 to check the view on sidelink | Huawei |
| R2-2004075 | [AT109bis-e][704][V2X] SIB12/28 (OPPO) | OPPO (Rapporteur) |
| R2-2004077 | Correct on SIB28 message for NR V2X | OPPO |
| R2-2004084 | LS to RAN1 to check the view on sidelink | RAN2 |
| R2-2004085 | Proposed easy agreements on RRC for 5G V2X with NR SL | Huawei (Rapporteur) |
| 6.4.2.2 | Others | |
| R2-2002604 | Open aspects on mode 2 operation | Intel Corporation |
| R2-2002638 | Summary of [Post109e#20] V2X Remaining UE capability issues (OPPO) | OPPO |
| R2-2002639 | Summary of capability related Tdoc submitted to R2#109bis-E | OPPO |
| R2-2002661 | Further issues on the mismatch of UE capabilities in unicast sidelink | Nokia, Nokia Shanghai Bell |
| R2-2002771 | Remaining Issues on NR V2X Resource Allocation for Zone Configuration | ITRI |
| R2-2002808 | Discussion on Interoperability of V2X UEs camped in different cells | Apple |
| R2-2002829 | Discussion on inter-RAT Cell Selection/Reselection | CATT |
| R2-2002830 | Introduce a new IE in SIB1 to indicate the anchor frequency only | CATT |
| R2-2002859 | Left issues on UE capability for NR V2X | LG Electronics France |
| R2-2003097 | Remaining issues of cell (re)selection for NR V2X | Lenovo, Motorola Mobility |
| R2-2003214 | UE capability left issue for NR V2X | Ericsson |
| R2-2003366 | Remaining issue on RRC state transition for groupcast | ITRI |
| R2-2003515 | Remaining issues on cell reselection for sidelink in TS 38.304 | Huawei, HiSilicon |
| R2-2003516 | Draft CR to TS 38.304 on cell (re)selection for sidelink | Huawei, HiSilicon |
| R2-2003603 | Clarification on cell reselection | CATT |
| R2-2003721 | Further discussion on cell reselection for V2X | Samsung Electronics Co., Ltd |
| R2-2003756 | Correction on cell reselection for V2X | Samsung Electronics Co., Ltd |
| R2-2003779 | Summary of NR V2X cell (re-)selection | ZTE Corporation |
| R2-2004081 | LS on UE capability | OPPO |
| R2-2004087 | LS on UE capability | RAN2 |
| 6.4.2.3 | ASN.1 issues | |
| R2-2002624 | Correction on SL configuration procedure [N009] | OPPO |
| R2-2002625 | Correction on SL configuration procedure [N009] | OPPO |
| R2-2002626 | Left issues on inter-RAT UAI configuration and CBR report [N038] | OPPO |
| R2-2002627 | Left issues on inter-RAT UAI configuration and CBR report [N038] | OPPO |
| R2-2002628 | Left issues on inter-RAT UAI configuration and CBR report [N038] | OPPO |
| R2-2002629 | Correction on RLF report via SUI message [N037, RIL-O306] | OPPO |
| R2-2002630 | Correction on RLF report via SUI message [N037, RIL-O306] | OPPO |
| R2-2002721 | Cleanup of requirements on maintenance of PC5-RRC connection [N.016][N.021] | MediaTek Inc. |
| R2-2003206 | [E035, E036, E042, E044, E045, E056, E062] Miscellaneous corrections for NR V2X | Ericsson |
| R2-2003207 | [E040, E060] Correction to AS configuration failure in NR V2X | Ericsson |
| R2-2003208 | [E059] Alignment of terminology for toAddModList and toReleaseList | Ericsson |
| R2-2003209 | [E055, E057, E058] Missing initiation actions in NR V2X RRC procedure | Ericsson |
| R2-2003210 | [E055, E057, E058] Missing initiation actions in NR V2X RRC procedure | Ericsson |
| R2-2003211 | [E061] Correction on sl-Failure in SidelinkUEInformation | Ericsson |
| R2-2003212 | [E046, E047] Correction to CBR measurements for V2X | Ericsson |
| R2-2003213 | [E046, E047] Correction to CBR measurements for V2X | Ericsson |
| R2-2003215 | [048] Missing RAN1 agreements to transmission of SLSS for NR V2X | Ericsson |
| R2-2003432 | Ambiguity on which SL carrier frequency to be released (N.040) | vivo |
| R2-2003433 | No CBR based PSSCH tx parameters configuration to mode 1 UE (N.041) | vivo |
| R2-2003434 | Sidelink communication reception (N.042) | vivo |
| R2-2003435 | Frequency resources configuration for actually used PSFCH transmissions (N.043) | vivo |
| R2-2003436 | Align PSFCH Configuration of TX and RX resource pools (N.044) | vivo |
| R2-2003517 | Discussion on Inter-RAT measurement reporting related issue for NR SL in TS 36.331 [N.011] | Huawei, HiSilicon |
| R2-2003518 | Draft CR on inter-RAT measurement reporting related issue in TS 36.331 [N.011] | Huawei, HiSilicon |
| R2-2003560 | Summary document of 6.4.2.3 for ASN.1 related issues in V2X session | Huawei, HiSilicon |
| R2-2003599 | Clarification on resource usage in case of exceptional cases [ Issue #N.026] | CATT |
| R2-2003600 | Clarification on sidelink RRC reconfiguration failure[ Issue #N.028] | CATT |
| R2-2003601 | Clarification on SUI transmission[ Issue #N.024] | CATT |
| R2-2003623 | Discussion on the SL configuration in CU-DU architecture | Huawei, HiSilicon |
| R2-2003624 | Draft LS on SL configuration in CU-DU architecture to R3 | Huawei, HiSilicon |
| R2-2003625 | Draft CR to support the SL configuration in CU-DU architecture | Huawei, HiSilicon |
| R2-2003673 | Clarification of SLRB configuration for IP SDU or non-IP SDU | Samsung Electronics Co., Ltd |
| R2-2003674 | Clarification of SLRB configuration for IP SDU or non-IP SDU | Samsung Electronics Co., Ltd |
| R2-2003675 | NR V2X TX profile configuration | Samsung Electronics Co., Ltd |
| R2-2003676 | NR V2X TX profile configuration | Samsung Electronics Co., Ltd |
| R2-2003677 | NR Sidelink PDCP out of order delivery configuration | Samsung Electronics Co., Ltd |
| R2-2003678 | NR Sidelink PDCP out of order delivery configuration | Samsung Electronics Co., Ltd |
| R2-2003679 | Clarification for SLRB configuration procedures | Samsung Electronics Co., Ltd |
| R2-2003680 | Clarification for SUI message transmission | Samsung Electronics Co., Ltd |
| 6.4.3.1 | MAC | |
| R2-2002558 | Remaining Issues_Sidelink CSI Reporting and Interruption handling | Samsung Electronics Co., Ltd |
| R2-2002559 | SR Trigger for Sidelink CSI Reporting | Samsung Electronics Co., Ltd |
| R2-2002565 | Discussion on NR V2X remaining MAC issues | ZTE Corporation, Sanechips |
| R2-2002568 | (draft)CR on TS 38.321 for NR V2X on miscellaneous issues | ZTE Corporation, Sanechips |
| R2-2002569 | (draft)CR on TS 36.321 for NR V2X on miscellaneous issues | ZTE Corporation, Sanechips |
| R2-2002603 | Miscellaneous MAC issues | Intel Corporation |
| R2-2002623 | Draft-CR on left issues of 38.321 | OPPO |
| R2-2002648 | Left issues on MAC running CR | OPPO |
| R2-2002809 | Remaining issues on NR V2X MAC Design | Apple |
| R2-2002831 | Remaining Issues on MAC | CATT |
| R2-2002832 | Clarification on the impact of configured grant and CSI MAC CE | CATT |
| R2-2002955 | Discussion on NR-V2X MAC left issues | Fujitsu |
| R2-2003025 | Clarification for UL/SL prioritization in MAC spec | MediaTek Inc. |
| R2-2003026 | Remaining MAC issues | MediaTek Inc. |
| R2-2003110 | MAC left issues | Ericsson |
| R2-2003112 | Correction on mode 2 resource selection procedure and SR configuration for SL CSI report | Ericsson |
| R2-2003116 | Remaining aspects of NR V2X Tx UE behavior | Lenovo, Motorola Mobility, Deutsche Telekom, Fraunhofer HHI and Fraunhofer IIS, Continental Automotive GmbH, MediaTek, Bosch |
| R2-2003122 | Remaining MAC Issues | Lenovo, Motorola Mobility |
| R2-2003224 | Groupcast HARQ feedback from RX UE without location information | Futurewei |
| R2-2003240 | Remaining MAC Issues for NR V2X | Interdigital |
| R2-2003292 | Discussion on LCH selection | Fraunhofer HHI, Fraunhofer IIS |
| R2-2003332 | SL groupcast with Option-2 HARQ | Nokia, Nokia Shanghai Bell |
| R2-2003398 | Remaining issues for SL-SCH MAC subheader | Qualcomm Finland RFFE Oy |
| R2-2003437 | Remaining MAC issues | vivo |
| R2-2003521 | Remaining Part of [Offline Disc#704] Identified proposals to V2X MAC | LG Electronics Inc. |
| R2-2003522 | Report of [Post109e#21] Remaining MAC Issues (LG) | LG Electronics Inc. |
| R2-2003523 | [Post109e#22] CR to 38.321 on Corrections to NR sidelink | LG Electronics Inc. |
| R2-2003524 | Remaining V2X MAC Issues | LG Electronics Inc. |
| R2-2003533 | Draft CR to 38.321 for MAC SL-SCH subheader | Qualcomm Finland RFFE Oy |
| R2-2003555 | Discussion on remaining MAC Open issues for 5G V2X with NR SL | Huawei, Hisilicon |
| R2-2003556 | Draft CR to TS 38.321 on remaining MAC Open issues for 5G V2X with NR SL | Huawei, Hisilicon |
| R2-2003557 | Draft CR to TS 38.331 on remaining MAC Open issues for 5G V2X with NR SL | Huawei, Hisilicon |
| R2-2003602 | Clarification on the impact of configured grant | CATT |
| R2-2003640 | Draft 38.321 CR on remaining MAC issues | vivo |
| R2-2003736 | Discussion on BSR prioritization issue | Beijing Xiaomi Mobile Software |
| R2-2003740 | Discussion on BSR prioritization issue | Beijing Xiaomi Mobile Software |
| R2-2003757 | Summary of MAC open issues for NR sidelink | LG Electronics France |
| R2-2003776 | Draft CR to 38.321 on SL process for reception | Qualcomm Finland RFFE Oy |
| R2-2004079 | [DRAFT] LS on Cast type indication | LGE |
| R2-2004082 | LS on Cast type indication and MAC agreements | RAN2 |
| 6.4.3.2 | Others | |
| R2-2002566 | Discussion on NR V2X remaining user plane issues | ZTE Corporation, Sanechips |
| R2-2002570 | (draft)CR on TS 38.323 for NR V2X on miscellaneous issues | ZTE Corporation, Sanechips |
| R2-2002649 | Discussion on PDCP open issues | OPPO |
| R2-2002650 | 38323_CRyyyy_(REL-16)_Correct on PDCP for NR V2X | OPPO |
| R2-2002810 | Remaining issues on NR V2X PDCP Design | Apple |
| R2-2002833 | Remaining Issues on PDCP | CATT |
| R2-2002834 | 38.323 draftCR for NR V2X | CATT |
| R2-2002861 | Left issue on SDAP for NR V2X | LG Electronics France |
| R2-2003111 | Report for email discussion Pose109e#19 V2X Remaining RLC issue | Ericsson |
| R2-2003113 | Editorial Corrections on SDAP for NR sidelink | Ericsson |
| R2-2003237 | Report on email discussion [Post109e#23][V2X] Remaining RLM/RLF Issue | InterDigital |
| R2-2003238 | Draft CR to 38.321 for HARQ-Based RLF at TX UE | InterDigital, Kyocera |
| R2-2003239 | Draft CR to 38.331 for HARQ-Based RLF at TX UE | InterDigital, Kyocera |
| R2-2003510 | Discussion on the SLRB PDCP header format | Huawei, HiSilicon |
| R2-2003511 | Draft CR on the PDCP format for NR SL unicast | Huawei, HiSilicon |
| R2-2003512 | Draft CR on the PDCP format for NR SL unicast | Huawei, HiSilicon |
| R2-2003535 | Draft CR to 38.323 for NR PC5-S and PDCP header | Qualcomm Finland RFFE Oy |
| R2-2003563 | RLF based on HARQ operation | ITL |
| R2-2003668 | Remaining PDCP issues | Nokia, Nokia Shanghai Bell |
| R2-2003681 | Discussion for SL PDCP open issues | Samsung Electronics Co., Ltd |
| R2-2003682 | SL PDCP COUNT wrap around avoidance and initial value of RX_DELIV | Samsung Electronics Co., Ltd |
| R2-2003683 | SL PDCP COUNT wrap around avoidance | Samsung Electronics Co., Ltd |
| R2-2003774 | Summary of PDCP remaining issues on NR V2X | CATT |
| R2-2003819 | Summary of NR V2X SDAP related contribution | vivo |
| R2-2004078 | Summary of offline discussion for PDCP remaining issues (CATT) | CATT (rapporteur) |
| R2-2004083 | LS response to SA3 on the security related issues for NR SL | RAN2 |
| R2-2004086 | LS on RLF Agreements | RAN2 |
| R2-2004180 | Report on email discussion [Post109e#23][V2X] Remaining RLM/RLF Issue | InterDigital |
| 6.5.1 | Organisational | |
| R2-2002725 | Work plan for RACS-RAN work item | MediaTek Inc., CATT |
| R2-2002726 | Work plan for RACS-RAN work item | MediaTek Inc., CATT |
| R2-2003290 | Correction to transfer of UE capabilities at HO for RACS (38.331) | ZTE Corporation, Ericsson,MediaTek Inc.,Sanechips |
| R2-2003305 | Correction to transfer of UE capabilities at HO for RACS (36.331) | MediaTek Inc., Ericsson, ZTE Corporation, Sanechips |
| R2-2003904 | Offline discussion 108: RACS Stage 3 CRs | ZTE (Rapporteur) |
| R2-2003905 | Correction to transfer of UE capabilities at HO for RACS (38.331) | ZTE Corporation, Ericsson,MediaTek Inc.,Sanechips |
| R2-2003906 | Correction to transfer of UE capabilities at HO for RACS (36.331) | MediaTek Inc., Ericsson, ZTE Corporation, Sanechips |
| R2-2004221 | Reply LS on RACS and signalling of UE capabilities at handover (S2-2003483; contact: Ericsson) | SA2 |
| R2-2004224 | LS on different coding formats (S2-2003507; contact: Samsung) | SA2 |
| 6.5.2 | Corrections | |
| R2-2002881 | Transfer of segmented UECapabilityInformation by SRB2 | Samsung |
| R2-2003471 | UE capability indication for segmentation | Huawei, HiSilicon |
| 6.7.1 | General | |
| R2-2002947 | Correction for NR IIOT in 38.321 | Samsung |
| R2-2003166 | Summary of IIOT WI agreements and open issues | Nokia (rapporteur) |
| R2-2004195 | Correction for NR IIOT in 38.321 | Samsung |
| 6.7.2.1 | Accurate reference timing | |
| R2-2002705 | On UE need for time synch | Ericsson |
| R2-2002706 | On encoding of reference time information | Ericsson |
| R2-2002752 | Remaining Issues on Accurate Reference Timing | CATT |
| R2-2002772 | UE report of the reference time interest | vivo |
| R2-2002940 | Reference Timing Delivery of gNB | Samsung |
| R2-2002976 | On-demand SI requesting for reference time information by connected UE | OPPO |
| R2-2002993 | On-demand SI request for RRC connected UEs | Huawei, HiSilicon |
| R2-2003167 | Remaining issues for accurate reference time delivery | Nokia, Nokia Shanghai Bell |
| R2-2003294 | FFS on accurate reference timing request | ZTE Corporation, Sanechips, China Southern Power Grid Co., Ltd |
| R2-2003397 | ASN.1 improvements for saving 32 bits in reference time in SIB9 | Qualcomm Incorporated |
| R2-2003404 | Draft CR 1 for On-demand SI request for RRC connected UEs | Huawei, HiSilicon |
| R2-2003406 | Draft CR 2 for On-demand SI request for RRC connected UEs | Huawei, HiSilicon |
| R2-2003505 | Remaining Issues for Accurate reference timing | CMCC |
| R2-2003738 | On-demand SI request for RRC connected UEs | Huawei, HiSilicon |
| R2-2003809 | Summary of 6.7.2.1 Accurate reference timing | vivo |
| R2-2004150 | [Report of [AT109bis-e][025][IIOT] Accurate Reference Timing (Vivo)] | vivo |
| 6.7.2.2 | Scheduling Enhancements | |
| R2-2002657 | Handling of collision between TSN transmission and measurement gap | Spreadtrum Communications |
| R2-2002663 | Discussion about open issues for CG and SPS | Huawei, HiSilicon |
| R2-2002707 | SPS CG remaining issues | Ericsson |
| R2-2002708 | TSC AI clarifications: meaning of arrival time | Ericsson |
| R2-2002709 | Draft LS: TSC AI clarifications for arrival time | Ericsson |
| R2-2002753 | Remaining issues for multiple SPS and CG configurations | CATT |
| R2-2002932 | Split secondary path for split bearer | LG Electronics Inc. |
| R2-2002933 | Absence of duplication state in moreThanTwoRLC | LG Electronics Inc. |
| R2-2002946 | Configuration of Configured Grant and Semi-Persistent Scheduling | Samsung |
| R2-2003168 | Periodicities of multiple of 2 or 7 symbols for CG | Nokia, Nokia Shanghai Bell, Ericsson, NTT Docomo |
| R2-2003169 | Determining the ‘closest N’ for CG Type-1 initialization | Nokia, Nokia Shanghai Bell |
| R2-2003497 | Summary of AI 6.7.2.2 IIoT Scheduling Enhancements | CMCC (Summary Rapporteur) |
| R2-2003504 | RRC Open Issues for Scheduling Enhancements | CMCC |
| R2-2003586 | Remaining issues on configured grant type 1 resources calculation | ZTE, Sanechips |
| R2-2004149 | Summary of offline discussion-026- Scheduling Enhancements | CMCC |
| R2-2004158 | Summary of offline discussion-026- Scheduling Enhancements | CMCC |
| 6.7.2.3 | Other | |
| R2-2002703 | Correction of NR IIOT | Ericsson |
| R2-2002704 | Correction of NR IIOT | Ericsson |
| R2-2002754 | DraftCR of RRC Open Issues | CATT |
| R2-2002974 | Draft-CR on RRC open issues of 38.331 | OPPO |
| R2-2002975 | Draft-CR on split transmission of 38.323 | OPPO |
| R2-2003377 | Draft CR on introduction of EHC in LTE | Huawei, HiSilicon |
| R2-2003526 | SPS Ack configuration in RRC | Qualcomm Incorporated |
| R2-2004233 | Summary on [AT109bis-e][027][IIOT] RRC (Ericsson) | Ericsson |
| 6.7.3.1 | Intra-UE prioritization and multiplexing | |
| R2-2002710 | Remaining issues on intra-UE prioritization and multiplexing | Ericsson |
| R2-2002774 | Transmission of Deprioritized PDU after CG Change | vivo |
| R2-2002775 | Clarification on the intra-UE prioritization per UE or per cell | vivo |
| R2-2002777 | Clarification on the generation of the two MAC PDUs | vivo |
| R2-2002778 | Discussion on the deprioritized CG | vivo |
| R2-2002779 | Remaining issues for SR and PUSCH collision | vivo |
| R2-2002877 | Align the Priority Handling for overlapping UL Grants between MAC and PHY | Sharp |
| R2-2002941 | Priority of SR Triggered by MAC CE | Samsung |
| R2-2002971 | Discussion on two MAC PDUs with the same L1 priority | OPPO, ZTE Corporation, Sanechips |
| R2-2002972 | Draft LS on two MAC PDUs with the same L1 priority | OPPO |
| R2-2003003 | Consideration on grant priority determination with MAC CE | LG Electronics Inc. |
| R2-2003023 | Consideration on delayed CG confirmation MAC CE | LG Electronics Polska |
| R2-2003027 | Consideration on sharing HARQ process in IIoT | LG Electronics Polska |
| R2-2003226 | Summary of e-mail discussion: [Post109e#50][IIOT] Remaining issues intra-UE prioritization | Nokia, Nokia Shanghai Bell |
| R2-2003363 | MAC handling of dropped SRs | InterDigital, Inc. |
| R2-2003590 | Discussion on the intra-UE collision case involving the Msg.3 | ZTE, Sanechips, OPPO |
| R2-2003591 | Remaining issue on the collision between SR and PUSCH | ZTE, Sanechips |
| R2-2003592 | Remaining issues on HARQ conflict between configured grant and dynamic grant | ZTE, Sanechips |
| R2-2003647 | Prioritization between CG and uplink grant for Msg3 or MSGA payload | ASUSTeK |
| R2-2003648 | Handling UL grant prioritization with non-overlapping PUSCH duration | ASUSTeK |
| R2-2004121 | LS on Intra-UE Prioritization | RAN2 |
| R2-2004130 | Summary of Offline Discussion [028]: Intra-UE prioritization and MAC, Part 1 | Nokia, Samsung |
| R2-2004230 | Offline-028: Intra-UE prioritization and MAC, Part 3 | Samsung |
| R2-2004257 | Offline-028: Intra-UE prioritization and MAC, Part 3 | Samsung |
| 6.7.3.2 | Other | |
| R2-2002942 | Remaining Issues on Intra-UE Prioritization | Samsung |
| R2-2002945 | De-prioritization by Other Deprioritized Grants | Samsung |
| R2-2003124 | Summary of MAC Open Issues and Corrections | Samsung |
| R2-2003225 | Autonomous transmission during BWP switch | Lenovo, Motorola Mobility |
| R2-2004289 | Correction for NR IIOT in 38.321 | Samsung |
| 6.7.4 | PDCP Open Issues and Corrections | |
| R2-2003587 | Remaining issues on enhanced PDCP duplication | ZTE, Sanechips |
| 6.7.4.1 | PDCP Duplication | |
| R2-2002656 | Discussion on efficient PDCP duplication base on configuration of gNB | Spreadtrum Communications |
| R2-2002711 | PDCP duplication open issues | Ericsson |
| R2-2002755 | Discussion on the Rel-15 Duplication MAC CE | CATT |
| R2-2002756 | Leftovers of PDCP Duplication | CATT |
| R2-2002757 | Discussion on LCH-to-Cell Restriction in Rel-16 PDCP Duplication | CATT |
| R2-2002776 | Discussion on the Rel-15 PDCP duplication MAC CE | vivo |
| R2-2002817 | Open issues for PDCP Duplication Enhancements | Apple |
| R2-2002862 | PDCP duplication states of the associated RLC entities when duplicationState is absent | Sharp |
| R2-2002934 | Use of Rel-15 Duplication MAC CE | LG Electronics Inc. |
| R2-2002935 | Issues when all secondary RLC entities are deactivated | LG Electronics Inc. |
| R2-2002943 | Open Issues on PDCP Duplication | Samsung |
| R2-2002956 | R15 MAC CE duplication on/off for R16 duplication on/off | Fujitsu |
| R2-2002977 | Coexist of R15 and R16 duplication (de-)activation MAC CE | OPPO |
| R2-2002978 | Application of Rel-15 MAC CE on Rel-16 duplication | OPPO |
| R2-2002995 | Open issues on PDCP duplication enhancements | Huawei, HiSilicon |
| R2-2003095 | Reuse R15 MAC CE on/off for R16 duplication | Lenovo, Motorola Mobility |
| R2-2003227 | Remaining Issues for PDCP Duplication | Nokia, Nokia Shanghai Bell |
| R2-2003320 | Remaining issues in PDCP duplication enhancements | Intel Corporation |
| R2-2003506 | Remaining Issues for PDCP Duplication | CMCC |
| R2-2003772 | Summary of A.I. 6.7.4.1 PDCP Duplication | LG Electronics Inc. (Summary rapporteur) |
| R2-2004170 | Summary of offline-029 PDCP Duplication | LG Electronics Inc. |
| R2-2004171 | 38323 CR Clarification on PDCP duplication | LG Electronics Inc. |
| R2-2004258 | NR PDCP corrections for NR IIOT | LG Electronics Inc. |
| R2-2004259 | LTE PDCP corrections for NR IIOT | LG Electronics Inc. |
| R2-2004283 | NR PDCP corrections for NR IIOT | LG Electronics Inc. |
| 6.7.4.2 | Ethernet Header Compression | |
| R2-2002669 | EHC absence of Q-Tags and NACK feedback | Sony |
| R2-2002712 | Remaining EHC issues | Ericsson |
| R2-2002718 | Discussion about remaining issues of EHC | Huawei, HiSilicon |
| R2-2002758 | The Remaining Issues on EHC | CATT |
| R2-2002773 | Reserved value in the EHC header | vivo |
| R2-2002908 | Leftover issues for EHC | Samsung |
| R2-2002936 | Length of CID field in EHC header | LG Electronics Inc. |
| R2-2002973 | Discussion on EHC format | OPPO |
| R2-2003171 | EHC remaining issues | Nokia, Nokia Shanghai Bell |
| R2-2003172 | Clarification on Ethernet frame handling by EHC | Nokia, Nokia Shanghai Bell |
| R2-2003296 | Remaining issues for EHC in TSC | ZTE Corporation, Sanechips |
| R2-2003321 | Remaining issues in Ethernet header compression | Intel Corporation |
| R2-2003758 | Remaining issue for EHC | NTT DOCOMO INC. |
| R2-2003782 | Summary on Ethernet Header Compression | Intel Corporation |
| R2-2003834 | Report of email discussion [AT109bis-e][030][IIOT] Ethernet Header Compression (Intel) | Intel Corporation |
| 6.7.5 | Stage-2 Corrections | |
| R2-2002994 | PDCP duplication terminology definition and impacts to cell restriction | Huawei, HiSilicon |
| R2-2003170 | Stage-2 updates for IIOT | Nokia, Nokia Shanghai Bell |
| R2-2003534 | Introduction of IIOT features to TS 37.340 | Huawei, HiSilicon |
| R2-2003755 | On reserved bit in EHC header | Qualcomm Incorporated |
| R2-2003887 | Stage-2 updates for IIOT (36.300) | Nokia, Nokia Shanghai Bell |
| R2-2003888 | Introduction of IIOT features to TS 37.340 | Huawei, HiSilicon |
| 6.7.6 | UE capabilities | |
| R2-2002713 | UE capability for IIoT | Ericsson |
| R2-2002759 | Remaining issues for UE capabilities | CATT |
| R2-2002815 | Discussion on DRBs Supported with Rel16 PDCP Duplication Enhancement | Apple |
| R2-2002816 | DRBs Supported with Rel16 PDCP Duplication Enhancement | Apple |
| R2-2002944 | UE Capability for IIOT | Samsung |
| R2-2003173 | UE feature list and capabilities remaining issues | Nokia, Nokia Shanghai Bell |
| R2-2003174 | UE radio access capabilities introduction for NR IIOT WI | Nokia, Nokia Shanghai Bell |
| R2-2003175 | UE feature list introduction for NR IIOT WI | Nokia, Nokia Shanghai Bell |
| R2-2003315 | Draft CR on introduction of miscellaneous EHC capabilities in LTE | Huawei, HiSilicon |
| R2-2003322 | Remaining issues in IIoT UE capability | Intel Corporation |
| R2-2003503 | RRC Open Issues for UE capabilities | CMCC |
| R2-2003732 | Open issues in Intra-UE prioritization capability | Qualcomm Incorporated |
| R2-2003793 | Summary of 6.7.6 UE capabilities for IIOT | Nokia, Nokia Shanghai Bell |
| R2-2003884 | UE radio access capabilities introduction for IIOT WI | Nokia, Nokia Shanghai Bell |
| R2-2003885 | UE radio access capabilities introduction for NR IIOT WI | Nokia, Nokia Shanghai Bell |
| R2-2003886 | UE feature list introduction for NR IIOT WI | Nokia, Nokia Shanghai Bell |
| R2-2004131 | Summary of: [AT109bis-e][031][IIOT] UE capabilities | Nokia, Nokia Shanghai Bell |
| R2-2004203 | Summary of: [AT109bis-e][031][IIOT] UE capabilities | Nokia, Nokia Shanghai Bell |
| 6.8.1 | Organisational | |
| R2-2002520 | LS on outcome of email discussions on aperiodic SRS for positioning configuration from RAN1#100e (R1-2001483; contact: Ericsson) | RAN1 |
| R2-2002529 | LS on gNB measurements report mapping for NR Positioning (R4-2002280; contact: Qualcomm) | RAN4 |
| R2-2003063 | Runnnig CR to MAC spec for R16 Positioning | Huawei, HiSilicon |
| R2-2003316 | Discussion on capabilities for NR positioning | Intel Corporation |
| R2-2003317 | Introduction of UE positioning capabilities | Intel Corporation |
| R2-2004219 | Reply LS on Local NR positioning in NG-RAN (S2-2003341; contact: Nokia) | SA2 |
| 6.8.2.1 | Stage 2 | |
| R2-2002913 | Clarification on UE Positioning Architecture in 38.305 for Rel-15 | CATT |
| R2-2002914 | Clarification on UE Positioning Architecture in 38.305 for Rel-16 | CATT |
| R2-2002939 | Discussion on reusing Rel-15 SRS for Multi-RTT | ZTE Corporation |
| R2-2003054 | DraftLS_RAN3_non-periodicSRSPositioning | Huawei, HiSilicon |
| R2-2003055 | DraftCR for SSB configuration in LPP spec | Huawei, HiSilicon |
| R2-2003056 | DraftCR for SSB configuration in RRC spec | Huawei, HiSilicon |
| R2-2003057 | DraftLS_RAN3_On Spatial relations for positioning | Huawei, HiSilicon |
| R2-2003060 | Text proposal to stage-2 specification | Huawei, HiSilicon |
| R2-2003068 | [Post109e-30][NRPos] Non-periodic SRS for positioning (Huawei) | Huawei, HiSilicon |
| R2-2003069 | [Post109e-31][Pos] Details of spatial relation for positioning (Huawei) | Huawei, HiSilicon |
| R2-2003348 | Various Corrections to NR Positioning | Qualcomm Incorporated |
| R2-2003396 | Text Proposal to clarify the meaning of GNSS term | ESA, Nokia, Nokia Shanghai Bell |
| R2-2003620 | Summary document for agenda item 6.8.2.1 - NR Positioning Stage 2 | Nokia, Nokia Shanghai Bell |
| R2-2003731 | On supporting of non-periodic SRS for positioning | Samsung R&D Institute UK |
| R2-2003984 | Draft Response LS on SRS and SSB configuration for NR Positioning | Intel |
| R2-2003985 | Correction on SSB configuration in LPP spec | Huawei, HiSilicon |
| R2-2003986 | Correction on SSB configuration in LPP spec | Huawei, HiSilicon |
| R2-2003987 | Correction on SSB configuration in LPP spec | Huawei, HiSilicon |
| R2-2003989 | Response LS on SRS and SSB configuration for NR Positioning | RAN2 |
| R2-2003990 | Various Corrections to NR Positioning | Qualcomm Incorporated |
| R2-2003991 | CR to clarify the meaning of GNSS term in 36.305 Rel-15 | ESA, Nokia, Nokia Shanghai Bell |
| R2-2003992 | CR to clarify the meaning of GNSS term in 36.305 Rel-16 | ESA, Nokia, Nokia Shanghai Bell |
| R2-2003993 | CR to clarify the meaning of GNSS term in 38.305 Rel-15 | ESA, Nokia, Nokia Shanghai Bell |
| R2-2003994 | CR to clarify the meaning of GNSS term in 38.305 Rel-16 | ESA, Nokia, Nokia Shanghai Bell |
| R2-2003995 | Clarification on UE Positioning Architecture in 38.305 for Rel-15 | CATT |
| R2-2003996 | Clarification on UE Positioning Architecture in 38.305 for Rel-16 | CATT |
| R2-2004143 | Clarification on UE Positioning Architecture in 38.305 for Rel-15 | CATT |
| R2-2004144 | Clarification on UE Positioning Architecture in 38.305 for Rel-16 | CATT |
| 6.8.2.2 | RRC | |
| R2-2002598 | Broadcast of additional assistance data | NextNav, AT&T, FirstNet, Intel, Polaris Wireless |
| R2-2002617 | Discussion on GAP configuration and request for NR positioning | vivo |
| R2-2003059 | DraftCR on LocationMeasurementIndication | Huawei, HiSilicon |
| R2-2003136 | Recommendation message from LMF to gNB for SRS configuration | Ericsson |
| R2-2003137 | UL SRS UE Capability | Ericsson |
| R2-2003729 | SSB configuration for DL-/UL-only method in RRC | Samsung R&D Institute UK |
| R2-2003769 | Summary of agenda item 6.8.2.2 for RRC | Huawei |
| R2-2003880 | Capturing RRC Positioning Impacts after RAN2-109bis | Ericsson (Rapporteur) |
| 6.8.2.3 | LPP | |
| R2-2002938 | Discussion on additional path reporting | ZTE Corporation |
| R2-2003061 | Remaining issues with LPP | Huawei, HiSilicon |
| R2-2003130 | Measurement Reporting for UE based positioning | Ericsson |
| R2-2003318 | Handling on TRP-ID | Intel Corporation |
| R2-2003730 | UE Rx – Tx time difference definition in LPP | Samsung R&D Institute UK |
| R2-2003783 | Summary of LPP agenda item 6.8.2.3 | Qualcomm Incorporated |
| R2-2003811 | Measurement Reporting for UE based positioning | Ericsson, Deutsche Telekom |
| R2-2003822 | Measurement Reporting for UE based positioning | Ericsson, Deutsche Telekom |
| R2-2003997 | Email discussion report: [AT109bis-e][610][POS] LPP proposals (Ericsson) | Ericsson |
| 6.8.2.4 | LPP ASN.1 issues | |
| R2-2002915 | Clarification on SFN0-Offset and DL-AoD report in LPP ASN.1 | CATT |
| R2-2003066 | DraftCR for NR-DL-PRS-Config | Huawei, HiSilicon |
| R2-2003067 | Miscellaneous Corrections to LPP ASN.1 | Huawei, HiSilicon |
| R2-2003143 | Overhead in current structure | Ericsson |
| R2-2003144 | Important LPP structural aspects | Ericsson |
| R2-2003349 | Various Corrections to NR Positioning | Qualcomm Incorporated |
| R2-2003350 | LPP clean-up | Qualcomm Incorporated |
| R2-2003781 | CR 37.355 V16.0.0, Corrections to the introduction of NR positioning | Ericsson |
| R2-2003981 | LPP Clean-Up | Qualcomm Incorporated |
| R2-2003982 | Email discussion report: [AT109bis-e][601][POS] LPP ASN.1 issue gathering and easy agreements (Qualcomm) | Qualcomm Incorporated |
| R2-2003983 | Email discussion report: [AT109bis-e][602][POS] LPP ASN.1 structural issues (Ericsson) | Ericsson |
| 6.8.2.5 | MAC | |
| R2-2002618 | Discussion on the impact of DRX on SRS for NR positioning | vivo |
| R2-2003062 | Correction to SP SRS actication deactivation MAC CE | Huawei, HiSilicon |
| R2-2003135 | Change LCID to eLCID for SP Positioning SRS Activation/Deactivation MAC CE | Ericsson |
| R2-2003768 | Running CR to MAC spec for R16 Positioning | Huawei, HiSilicon |
| R2-2003877 | LS on positioning SRS during DRX inactive time | RAN2 |
| R2-2003988 | Running CR for MAC spec for R16 positioning | Huawei, HiSilicon |
| R2-2004208 | Summary on MAC proposals under 6.8.2.5 | Huawei, HiSilicon |
| 6.8.2.6 | Broadcast assistance data | |
| R2-2002916 | Summary of the agreement and left issues on Broadcast Assistance Data | CATT |
| R2-2003058 | DraftCR for on-demand SI request for positioning | Huawei, HiSilicon |
| R2-2003132 | On the need of unicast tag for positioning si-BroadcastStatus | Ericsson |
| R2-2003140 | On Relevance of Broadcast | Ericsson |
| R2-2003607 | Summary for Broadcast of Assistance Data | CATT |
| R2-2003810 | On the need of unicast tag for positioning si-BroadcastStatus | Ericsson, Deutsche Telekom |
| R2-2003889 | Post109bis-e][xx][POS] Open issues on on-demand SI for positioning (Ericsson) | Ericsson |
| R2-2004209 | [AT109bis-e][056][OdSIBconn] On demand SI Open issue for positioning | Ericsson |
| 6.8.2.7 | UE-based positioning | |
| R2-2003064 | Discussion on UE-based positioning | Huawei, HiSilicon |
| R2-2003145 | Remaining issues with NR RAT dependent UE-based positioning | Ericsson |
| 6.8.3 | Other | |
| R2-2003065 | Discussion on UL-ECID | Huawei, HiSilicon |
| R2-2003376 | On UE RxTx Measurements | Ericsson |
| 6.9.1 | Organisational | |
| R2-2002744 | Corrections to Mobility Enhancements | Nokia, Intel Corporation (Rapporteurs) |
| R2-2003368 | UE Capability for Rel-16 NR mobility enhancement | Intel Corporation |
| R2-2003369 | UE Capability for Rel-16 NR mobility enhancement | Intel Corporation |
| R2-2003850 | 38.331 CR on NR MOB | Intel Corporation |
| R2-2003851 | 36.331 CR on NR MOB | Intel Corporation |
| R2-2003857 | Corrections to Mobility Enhancements | Nokia, Intel Corporation (Rapporteurs) |
| 6.9.2 | Reduction in user data interruption during DAPS handover | |
| R2-2002589 | RoHC handling during DAPS handover without key change | Ericsson |
| R2-2002799 | Non-DAPS DRB Handling when fallback to source | Apple |
| R2-2002863 | Discussion on consecutive ROHC failure | LG Electronics Inc. |
| R2-2003042 | Discussion on DAPS HO without key change | Huawei, HiSilicon |
| 6.9.3.1 | Open issues and corrections for conditional handover | |
| R2-2002748 | On measurement and evaluation during CHO execution | Futurewei |
| R2-2002900 | T304 running issue when CHO Execution | LG Electronics Inc. |
| R2-2002951 | Discussion of some remaining issues for CHO | OPPO |
| R2-2002996 | Corrections to conditional reconfiguration evaluation | PANASONIC R&D Center Germany |
| R2-2003035 | CHO and MR-DC operation | Ericsson |
| R2-2003105 | E-mail discussion report [Post109e#12][MOB] Resolving open issues for CHO | Nokia, Nokia Shanghai Bell |
| R2-2003106 | MCG recovery versus recovery via CHO - Rel-16 impact | Nokia, Nokia Shanghai Bell |
| R2-2003260 | Further details of CHO configuration and execution | China Telecom |
| R2-2003333 | Clarification on source reconfigiration during CHO | Samsung |
| R2-2003422 | Further consideration on conventional HO overriding a CHO command | ZTE Corporation, Sanechips |
| R2-2003577 | Discussion on leftovers for CHO | Huawei, HiSilicon |
| R2-2003609 | UE configuration release in RRC reestbalishment | SHARP |
| R2-2003847 | Report from [AT109bis-e][207][MOB] Open CHO issues | Nokia, Nokia Shanghai Bell |
| 6.9.3.2 | Open issues and corrections for fast handover failure recovery | |
| R2-2002599 | Discussions on VarRLF-Report Setting | Quectel |
| R2-2002901 | Failure handling of both CHO and MR-DC | LG Electronics Inc. |
| R2-2003036 | Failure handling interaction | Ericsson |
| R2-2003578 | Discussion on T312 support | Huawei, HiSilicon |
| R2-2003848 | Offline discussion 208: Finalization of T312 for Fast handover failure recovery | Samsung (Offline rapporteur) |
| 6.9.3.3 | UE capabilities for conditional handover and fast handover failure recovery | |
| R2-2002902 | Consideration on CHO capability | LG Electronics Inc. |
| R2-2003028 | UE capabilities for CHO and NR T312 | Nokia, Nokia Shanghai Bell |
| R2-2003037 | UE capabilities for CHO | Ericsson |
| R2-2003579 | Discussion on UE capabilities for CHO and T312 | Huawei, HiSilicon |
| 6.9.4.1 | Open issues and corrections for Conditional PSCell change for intra-SN | |
| R2-2002749 | Clarifications on issues of CPC-intra-SN | Futurewei |
| R2-2002800 | CPC with SRB3 Configuration | Apple |
| R2-2002903 | Left Issues for CPC in R16 | LG Electronics Inc. |
| R2-2003038 | Remaining issues for conditional PSCell change | Ericsson |
| R2-2003100 | Remaining issues for CPC | Lenovo, Motorola Mobility |
| R2-2003107 | On how to close the open issues for Conditional PSCell Change | Nokia, Nokia Shanghai Bell |
| R2-2003327 | Discussion on CPC configuration handling during SCG Release | Samsung |
| R2-2003423 | Remaining issues for CPC | ZTE Corporation, Sanechips |
| R2-2003440 | Report of [post109e@13][NR MOB] Resolving open issues for CPC | CATT |
| R2-2003441 | Draft CR for transmission of RRCReconfigurationComplete upon CPC execution | CATT |
| R2-2003442 | Draft CR for transmission of RRCReconfigurationComplete upon CPC execution | CATT |
| R2-2003580 | Discussion the transaction id issues for CPAC | Huawei, HiSilicon |
| R2-2003799 | Draft CR for transmission of RRCReconfigurationComplete upon CPC execution | CATT |
| R2-2003849 | Report of [AT109bis-e][209][NR MOB] Resolution to remaining open issues of CPC | CATT (offline discussion rapporteur) |
| 6.9.4.2 | UE capabilities for Conditional PSCell change for intra-SN | |
| R2-2002904 | Consideration on CPC capability | LG Electronics Inc. |
| R2-2003029 | UE capabilities for CPC | Nokia, Nokia Shanghai Bell |
| R2-2003039 | UE capabilities for conditional PSCell change | Ericsson |
| R2-2003581 | Discussion on UE capabilities for CPC | Huawei, HiSilicon |
| 6.9.5 | ASN.1 review of mobility WIs for NR RRC | |
| R2-2003326 | [S350] Discussion on radio bearer handling in DAPS | Samsung |
| R2-2003424 | [Z255] Correction for Pcell change in case of CPC | ZTE Corporation, Sanechips |
| R2-2003664 | [H223] Correction on TAG configuration applied to target cell | Huawei, HiSilicon |
| R2-2003844 | Report of [AT109bis-e][210][MOB ASN1] ASN.1 discussion for LTE and NR mobility (Intel/Ericsson) | Intel Corporation, Ericsson |
| 6.10.1 | General | |
| R2-2002517 | LS on uplink power control for NR-NR Dual-Connectivity (R1-2001421; contact: Apple) | RAN1 |
| R2-2003381 | CR for 36.331 for CA/DC Enhancements | Ericsson |
| R2-2003382 | CR for 38.331 on CA/DC Enhancements | Ericsson |
| R2-2003383 | Report on email discussion [Post109e][037][DCCA] RRC open issues (Ericsson) | Ericsson |
| R2-2003659 | [Coordinated][DCCA-H01] Adding p-MaxEUTRA, p-MaxUE-FR1, tdm-PatternConfig in RRCConnectionResume message | Huawei, HiSilicon |
| R2-2003660 | [Coordinated][DCCA-H01] Draft CR for adding p-maxEUTRA, p-maxUE-FR1, tdm-patternConfig in RRCConnectionResume message | Huawei, HiSilicon |
| R2-2003661 | [Coordinated][DCCA-H03] Correction on HARQ parameters configured for secondary PUCCH cell group | Huawei, HiSilicon |
| R2-2003662 | [Coordinated][DCCA-H03] Draft CR on HARQ parameters configured for secondary PUCCH cell group in TS 38.331 | Huawei, HiSilicon |
| R2-2003703 | Introducing of UE capabilities for eDCCA | Huawei, HiSilicon |
| R2-2003704 | Introduction of UE capabilities for eDCCA | Huawei, HiSilicon |
| R2-2003705 | Introducing of UE capabilities for eDCCA | Huawei, HiSilicon |
| R2-2003706 | Introducing of UE capabilities for eDCCA | Huawei, HiSilicon |
| R2-2003718 | Misc. ASN.1 corrections to 36.331 for eDCCA | Huawei, HiSilicon |
| R2-2003719 | Misc. ASN.1 corrections to 38.331 for eDCCA | Huawei, HiSilicon |
| R2-2003760 | [Coordinated][DCCA-H01] Adding p-MaxEUTRA, p-MaxUE-FR1, tdm-PatternConfig in RRCConnectionResume message | Huawei, HiSilicon |
| R2-2003761 | [Coordinated][DCCA-H01] Draft CR for adding p-maxEUTRA, p-maxUE-FR1, tdm-patternConfig in RRCConnectionResume message | Huawei, HiSilicon |
| R2-2003762 | [Coordinated][DCCA-H03] Correction on HARQ parameters configured for secondary PUCCH cell group | Huawei, HiSilicon |
| R2-2003763 | [Coordinated][DCCA-H03] Draft CR on HARQ parameters configured for secondary PUCCH cell group in TS 38.331 | Huawei, HiSilicon |
| R2-2003789 | Feature summary for DCCA RRC open issues | Ericsson |
| R2-2003881 | CR for 36.331 for CA/DC Enhancements | Ericsson (Rapporteur) |
| R2-2003882 | CR for 38.331 on CA/DC Enhancements | Ericsson (Rapporteur) |
| R2-2004120 | Report on offline discussion [AT109bis-e][032][DCCA] RRC | Ericsson |
| 6.10.2 | UE capabilities | |
| R2-2002642 | Remaining issues of UE capability of Rel-16 DCCA enhancement in TS 36.306 | Qualcomm Incorporated, Samsung |
| R2-2002643 | Remaining issues of UE capability of Rel-16 DCCA enhancement in TS 38.306 | Qualcomm Incorporated, Samsung |
| R2-2002769 | Remaining issue on DCCA capability | MediaTek Inc. |
| R2-2002892 | Remaining Issues on UE Capability for DC/CA Enhancement | vivo |
| R2-2003276 | Remaining issues for CA&DC UE capabilities | Ericsson |
| R2-2003707 | Summary for UE capabilities | Huawei, HiSilicon |
| R2-2003708 | UE capability for eDCCA RAN1 features | Huawei, HiSilicon |
| 6.10.3 | NR-NR Dual Connectivity | |
| R2-2002893 | T_offset determination for NR-DC dynamic power sharing | vivo |
| R2-2002894 | Draft CR on T_offset determination for NR-DC dynamic power sharing | vivo |
| R2-2002895 | Draft LS on T_offset determination for NR-DC dynamic power sharing | vivo |
| R2-2002959 | NR DC power control | Nokia, Nokia Shanghai Bell |
| R2-2002960 | LS answer to RAN1 on NR DC UL PC | Nokia, Nokia Shanghai Bell |
| R2-2002979 | NR DC power control | Nokia, Nokia Shanghai Bell |
| R2-2002980 | Reply LS on uplink power control for NR-NR Dual-Connectivity | Nokia, Nokia Shanghai Bell |
| R2-2003198 | Discussion on Toffset for NR-DC power control | Ericsson |
| R2-2003655 | Discussion on RAN2 impact for NR-DC Dynamic Power Sharing | Huawei, HiSilicon |
| R2-2003656 | Support of NR-DC semi-static power control Alt1-2 in Async CA | Huawei, HiSilicon |
| R2-2003657 | [Draft] LS on slot offset exchange for NR-DC power control | Huawei, HiSilicon |
| R2-2004184 | Report of [AT109bis-e][034][DCCA] NR-NR DC part 1. | Huawei, HiSilicon |
| R2-2004187 | [DRAFT] LS reply on uplink power control for NR-NR Dual-Connectivity | Apple |
| R2-2004189 | Further discussion on LS reply to RAN1 on NR-NR DC | Nokia, Nokia Shanghai Bell, Ericsson, ZTE, CATT, NTT DOCOMO, Verizon, T-Mobile USA |
| R2-2004196 | LS reply on uplink power control for NR-NR Dual-Connectivity | RAN2 |
| 6.10.4 | Early measurement reporting | |
| R2-2002644 | Remaining issues of NR early measurements | Qualcomm Incorporated |
| R2-2002675 | [RIL402]Introduction of secondary SMTC for early measurement configuration | OPPO |
| R2-2002701 | Remaining issues of early measurement | ZTE Corporation, Sanechips |
| R2-2003200 | Reporting early measurements to SN in INM | Ericsson |
| R2-2003217 | Consideration on conditions for cells to be reported | LG Electronics Inc. |
| R2-2003218 | Need codes for Ies in ssb-MeasConfig in NR SIB11 | LG Electronics Inc. |
| R2-2003220 | Consideration on conditions for cells to be reported | LG Electronics Inc. |
| R2-2003221 | Need codes for Ies in ssb-MeasConfig in NR SIB11 | LG Electronics Inc. |
| R2-2003384 | Early measurement configuration in UE context retrieval | Ericsson, Qualcomm Incorporated, LG Electronics Inc., CATT, OPPO, AT&T, Vodafone, Telecom Italia S.p.A, Intel Corporation, InterDigital Inc. |
| R2-2003385 | Granular reporting of early measurement results | Ericsson, MediaTek Inc., ZTE Corporation, LG Electronics Inc., Vivo, AT&T, Vodafone, InterDigital Inc., Telecom Italia S.p.A |
| R2-2003395 | Progressing some unresolved early measurement reporting issues | Samsung Telecommunications |
| R2-2003790 | Feature summary for early measurements | Ericsson |
| 6.10.5 | Fast SCell activation | |
| R2-2002646 | Remaining issues of dormant BWP | Qualcomm Incorporated |
| R2-2002673 | Discussion on implicit BFD-RS on dormant BWP | OPPO |
| R2-2002674 | Corrections on PHR generation due to dormant BWP | OPPO |
| R2-2002702 | Remaining issues of fast SCell activation | ZTE Corporation, Sanechips |
| R2-2002750 | Further discussion on Scell domancy | Futurewei |
| R2-2002768 | Discussion on first non-dormant UL BWP | MediaTek Inc. |
| R2-2002789 | Correction on the Configuration of sCellState [C101] [C102] | CATT |
| R2-2002801 | BFD-RS Configuration on Dormant BWP | Apple |
| R2-2002822 | CR to 38.331 on on supporting implicit BFD-RS configuration in dormant BWP | Qualcomm Incorporated |
| R2-2002899 | UL BWP behavior for dormancy | Samsung |
| R2-2002906 | Beam failure detection for dormancy | Samsung |
| R2-2002907 | Beam failure detection for dormancy | Samsung |
| R2-2002961 | On early measurements related to SCG CA | Nokia, Nokia Shanghai Bell |
| R2-2002962 | Remaining details of MCG failure recovery | Nokia, Nokia Shanghai Bell |
| R2-2002963 | BFD on Dormant Scell | Nokia, Nokia Shanghai Bell |
| R2-2002981 | Stage-2 dormant cleanup | Nokia, Nokia Shanghai Bell |
| R2-2002982 | MAC Dormant cleanup | Nokia, Nokia Shanghai Bell |
| R2-2002983 | RRC Dormant cleanup | Nokia, Nokia Shanghai Bell |
| R2-2003033 | Consideration on configuration of BFD-RS | LG Electronics Inc. |
| R2-2003277 | Correction to SCell activation procedures | Ericsson |
| R2-2003313 | PDSCH-Config for dormant BWP | LG Electronics Inc. |
| R2-2003658 | Corrections on MAC spec for direct SCell activation and dormant BWP | Huawei, HiSilicon |
| R2-2003770 | Summary of fast SCell activation | OPPO |
| R2-2004122 | Email report of [AT109bis-e][036][DCCA] Fast Scell Activation (OPPO) | OPPO |
| R2-2004123 | 38321CR Corrections on dormant BWP operation | OPPO |
| R2-2004183 | 38321CR Corrections on dormant BWP operation | OPPO |
| 6.10.6 | MCG SCell and SCG Configuration with RRC Resume | |
| R2-2002699 | Remaining issues of restoreSCG in RRC resume | ZTE Corporation, Sanechips |
| R2-2003128 | Remaining issue on stored SCG context | LG Electronics Inc. |
| R2-2003146 | Draft LS to RAN3 on updated Inactive AS context | LG Electronics Inc. |
| R2-2003241 | Draft 36.331 CR for Handling SCG Configuration in Resume | InterDigital, Ericsson, LG, OPPO |
| R2-2003242 | Draft 38.331 CR for Handling SCG Configuration in Resume | InterDigital, Ericsson, LG, OPPO |
| R2-2003243 | Handling the SCG Configuration in RRC Resume | InterDigital, Ericsson, LG, OPPO, KT Corp |
| R2-2003812 | Summary of MCG SCell and SCG Configuration with RRC Resume | ZTE Corporation |
| R2-2004129 | Report of [AT109bis-e][038][DCCA] MCG SCell and SCG with RRC Resume | ZTE Corporation |
| R2-2004141 | Report of [AT109bis-e][038][DCCA] MCG SCell and SCG with RRC Resume | ZTE Corporation |
| R2-2004242 | LS on updated Inactive AS context | RAN2 |
| 6.10.7 | Fast MCG link Recovery | |
| R2-2002647 | Remaining issues in Fast MCG Recovery | Qualcomm Incorporated |
| R2-2002700 | Support of Inter-RAT handover upon MCG failure recovery | ZTE Corporation, Sanechips |
| R2-2002790 | Correction on the Configuration of T316 [C103] [C104] | CATT |
| R2-2002964 | BFR on Dormant Scell | Nokia, Nokia Shanghai Bell |
| R2-2002984 | Erroneous instances of “the procedure ends” impacting reception over SRB3 | Nokia, Nokia Shanghai Bell |
| R2-2002992 | CR37340 on fast MCG recovery support | vivo |
| R2-2003199 | Summary of [Post109e#27][DCCA] Fast MCG recovery | Ericsson |
| R2-2003425 | [Z301] Correcction for SCG RLC failure during fast MCG recovery | ZTE Corporation, Sanechips |
| R2-2003839 | Summary of [AT109bis-e][039][DCCA] Fast MCG Link Recovery | Ericsson |
| R2-2004248 | Draft LS on Support of inter-rat HO for fast MCG recovery | Ericsson |
| R2-2004276 | LS on Support of inter-rat HO for fast MCG recovery | RAN2 |
| 6.10.8 | Other | |
| R2-2003709 | CG fast recovery via alternative UL | Huawei, HiSilicon |
| 6.11.1 | Organisational | |
| R2-2002601 | Report of email discussion [Post109e#42][PowSav] UE capabilities | Intel Corporation |
| R2-2002602 | UE capabilities for Rel-16 Power Saving (PWS) WI | Intel Corporation |
| R2-2002842 | SRB3 for reporting UAI for power saving | OPPO |
| 6.11.2 | PDCCH-based power saving signals/channel Additional stage-3 RAN2 aspects | |
| R2-2002797 | PDCCH-WUS Mechanism | Apple |
| R2-2002839 | Remaining issues of DCP impact on SCell dormancy | OPPO |
| R2-2002866 | Remaining issues for DCP | vivo |
| R2-2002930 | Correction on RAR and DCP monitoring | Nokia, Nokia Shanghai Bell |
| R2-2003032 | Remaining issue on DCP monitoring within RAR window | LG Electronics Inc. |
| R2-2003129 | Miscellaneous corrections to 38.321 for Rel-16 UE power saving | Huawei, HiSilicon |
| R2-2003288 | Open issues UE capability, DCP, UE assistance and RRM relaxation | Ericsson |
| R2-2003378 | Summary of [Post109e#41] [PowSav] DCP open issues – Phase 1 | InterDigital |
| R2-2003379 | Report of [Post109e#41] [PowSav] DCP open issues | InterDigital |
| R2-2003562 | PDCCH-based power saving signal/channel | Samsung |
| R2-2003955 | [AT109bis-e][506][PowSav] Open Issues for DCP | InterDigital (Email discussion rapporteur) |
| R2-2003956 | Miscellaneous corrections to 38.321 for Rel-16 UE power saving | Huawei, HiSilicon |
| R2-2003963 | LS on RAN2 DCP Open Issues | InterDigital |
| R2-2003967 | LS on RAN2 DCP Open Issues | InterDigital |
| R2-2003969 | LS on RAN2 DCP Open Issues | InterDigital |
| R2-2003975 | MAC CR for Rel-16 UE power saving | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
| R2-2004175 | LS on RAN2 DCP Open Issues | RAN2 |
| 6.11.3 | UE assistance and RRC | |
| R2-2002670 | Power Saving UE assistance information | Sony |
| R2-2002798 | Value Range for UE Assistance Information | Apple |
| R2-2002838 | Remaining issues on implicit SCG release | OPPO |
| R2-2003125 | CR for 38.331 for Power Savings | MediaTek Inc. |
| R2-2003126 | CR for 36.331 for Power Savings | MediaTek Inc. |
| R2-2003127 | Summary of [Post109e#43][PowSav] UE Assistance and RRC open issues | MediaTek Inc. |
| R2-2003229 | Adopting general UE assistance reporting framework to UE power saving | Samsung Telecommunications |
| R2-2003289 | UE assistance for connection release | Ericsson, ZTE, Deutsche Telekom |
| R2-2003387 | Adopting general UE assistance reporting framework to UE power saving | Samsung Telecommunications |
| R2-2003472 | Discussion on clarification for max MIMO layer and antenna port | Huawei, HiSilicon |
| R2-2003473 | TP for clarification for max MIMO layer and antenna port | Huawei, HiSilicon |
| R2-2003957 | Summary of [Post109e#43][PowSav] UE Assistance and RRC open issues and Tdocs | MediaTek Inc. (Rapporteur) |
| R2-2003964 | [DRAFT] LS on NR SCG release for power saving | MediaTek |
| R2-2003968 | LS on NR SCG release for power saving | RAN2 |
| 6.11.6 | RRM measurement relaxation | |
| R2-2002665 | UE power saving for inter frequency measurements | Sony |
| R2-2002735 | Configurations for RRM Measurement Relaxation | MediaTek Inc. |
| R2-2002791 | Report of [Post109e#44][PowSav] RRM open issues | CATT |
| R2-2002865 | CR on 38.304 for UE Power saving in NR | vivo |
| R2-2002867 | Configurations for RRM Measurement Relaxation | vivo |
| R2-2002950 | Correction of SI update of relaxed measurement parameters | Nokia, Nokia Shanghai Bell, Ericsson |
| R2-2003216 | EMR issue on relaxed measurement | LG Electronics Inc. |
| R2-2003219 | EMR issue on relaxed measurement | LG Electronics Inc. |
| R2-2003954 | [AT109bis-e][505][PowSav] RRM Open Issues | CATT |
| R2-2003958 | [AT109bis-e][505][PowSav] RRM Open Issues | CATT |
| R2-2003959 | CR on 38.304 for UE Power saving in NR | vivo |
| 6.12 | SON/MDT support for NR | |
| R2-2003324 | Draft reply LS on the status update of the SON support for NR works | Intel Corporation |
| 6.12.1 | General | |
| R2-2002521 | Reply LS on QoS monitoring for URLLC (R3-201372; contact: Intel) | RAN3 |
| R2-2002524 | LS on removal of Management Based MDT Allowed IE for NR (R3-201437; contact: Qualcomm) | RAN3 |
| R2-2002544 | Reply to LS to SA5 on trace related configurations for NR MDT (S5-201424; contact: Ericsson) | SA5 |
| R2-2002545 | LS on the status update of the SON support for NR works (S5-201525; contact: Intel) | SA5 |
| R2-2002896 | Running CR to 38.306 for NR_SON_MDT | vivo, CMCC |
| R2-2003487 | draft TS 38.314 | CMCC |
| R2-2003488 | UE Feature List for Rel-16 SON/MDT WI | CMCC |
| R2-2003797 | Summary on ASN1 RIL for MDT and SON | Huawei, HiSilicon |
| R2-2003871 | Summary of [Post109bis-e][900][MDTSON] CR to 38.331 | Huawei, Ericsson |
| R2-2003872 | Corrections on MDT and SON in NR | Huawei, Ericsson |
| R2-2003873 | Corrections on MDT and SON | Huawei, Ericsson |
| R2-2003874 | NR; Layer 2 Measurements | CMCC |
| R2-2004002 | Summary on ASN1 RIL for MDT and SON | Huawei |
| R2-2004220 | Reply LS on QoS Monitoring for URLLC (S2-2003468; contact: Huawei) | SA2 |
| R2-2004254 | Reply LS on the feasibility of Received Interference Power measurement (R1-2002932; contact: Huawei) | RAN1 |
| 6.12.2 | MDT | |
| R2-2002555 | Clarification of MDT Initiation in NR and NG-RAN | Qualcomm Incorporated, Nokia |
| R2-2002606 | Remaining Issues of UE Location Information | Qualcomm Incorporated |
| R2-2002731 | [C201 C203 C204] Discussion on Location Related Measurement Collection in MDT | CATT |
| R2-2002732 | [C201 C203 C204] Corrections on Location Related Measurement Collection in MDT | CATT |
| R2-2002733 | [C253 C256 C257] Discussion for CEF Report | CATT |
| R2-2002747 | [C253 C256 C257] Corrections for CEF Report | CATT |
| R2-2002826 | Remaining issues for NR MDT: [S461] [S462] [S463] [S464] [S465] [S466] [S467] [S468] [S469] [S470] [S471] [S474] | Samsung |
| R2-2002925 | CR to 37320 on MDT configuration | ZTE Corporation, Sanechips |
| R2-2003074 | Open issues associated of MDT | Ericsson |
| R2-2003076 | [E002] On mobilityState reporting | Ericsson |
| R2-2003084 | [E010] On stopping T330 upon going to idle | Ericsson |
| R2-2003085 | [E012] On logging TAC in CEF report | Ericsson |
| R2-2003086 | [E014] On WLAN, Bluetooth and sensor information transfer from LoggedMeasurementConfgiuration to VarLogMeasConfig | Ericsson |
| R2-2003087 | [E018] On procedural text correction for any cell selection state exiting in outOfCoverage event driven logged MDT | Ericsson |
| R2-2003088 | [E021] On any-cell selection state related logging in logged MDT | Ericsson |
| R2-2003091 | [E026] On creation of MeasQuantityResultsLogged-r16 | Ericsson |
| R2-2003093 | [E041] On changing serving cell CGI to optional in logged MDT report | Ericsson |
| R2-2003104 | CR to 37.320 on MDT initiation | ZTE Corporation, Sanechips |
| R2-2003117 | [C255] Reporting Logged MDT Result in SRB2 without DRB Establishment | CATT |
| R2-2003118 | [C265] Corrections on Recording the UE History Information | CATT |
| R2-2003120 | Introduction of TAC Information in CEF Report | CATT |
| R2-2003121 | Miscellaneous corrections for 37.320 | CATT |
| R2-2003158 | Resolving MDT stage 2 open issues | Nokia, Nokia Shanghai Bell |
| R2-2003159 | Miscellaneous corrections | Nokia (Rapporteur) |
| R2-2003160 | N011, N012, N013, N014 on PLMN Id association with cell Id | Nokia, Nokia Shanghai Bell |
| R2-2003161 | N015 on referencing TS23.122 | Nokia, Nokia Shanghai Bell |
| R2-2003499 | Removal of Management Based MDT Allowed IE for NR MDT | CMCC |
| R2-2003500 | CR for Removal of Management Based MDT Allowed IE for NR MDT | CMCC |
| R2-2003574 | Minor issues on MDT | Huawei, HiSilicon |
| R2-2003798 | Summary on MDT | Huawei, HiSilicon |
| R2-2003879 | Miscellaneous corrections | CMCC, Nokia, Nokia Shanghai Bell |
| R2-2004001 | Proposals for approval | CMCC |
| R2-2004003 | Summary on open issues on MDT | Huawei |
| 6.12.3 | L2 measurements | |
| R2-2002751 | Discussion on metric of number of active UEs in RRC connected | NTT DOCOMO INC. |
| R2-2002897 | Remaining issues on L2 measurement | vivo |
| R2-2002898 | CR37320 for M5 ~ M7 | vivo |
| R2-2003073 | Open issues of L2 measurements | Ericsson |
| R2-2003165 | Correction of DL packet delay | Nokia, Nokia Shanghai Bell |
| R2-2003486 | Summary of AI 6.12.3 L2 measurements | CMCC (Summary Rapporteur) |
| R2-2003489 | Miscellaneous corrections for draft TS 38.314 | CMCC |
| R2-2003575 | Minor issues on L2M | Huawei, HiSilicon |
| R2-2004005 | Summary for open issues for AI 6.12.3 L2 measurements | CMCC |
| 6.12.4 | SON | |
| R2-2002562 | Corrections to RA Report_S480_S481_S482_S483_S484_S485 | Samsung Electronics Co., Ltd |
| R2-2002720 | Remaining Aspects on UE History Information | Mediatek Inc. |
| R2-2002760 | Discussion on terminology of handover failure in rel-16 SON MDT | NTT DOCOMO INC. |
| R2-2002761 | Discussion on UE capability for location reporting in SCG failure | NTT DOCOMO INC. |
| R2-2002827 | Remaining issues for NR SON: [S472] [S473] [S475] [S476] [S477] [S478] [S479] | Samsung |
| R2-2002923 | [Z152] Correction to RACH report and RLF report | ZTE Corporation, Sanechips |
| R2-2002924 | Enhancement on RLF report for MRO | ZTE Corporation, Sanechips |
| R2-2003075 | Open issues associated to SON functions | Ericsson |
| R2-2003077 | [E007] On including TAC information for re-establishment cell in RLF report | Ericsson |
| R2-2003080 | [E009] On LTE previousPCell inclusion in NR RLFReport | Ericsson |
| R2-2003081 | [E009] On NR previousPCell inclusion in LTE RLFReport | Ericsson |
| R2-2003082 | [E009] On UE capabilities for inter-RAT MRO related RLF reporting | Ericsson |
| R2-2003083 | [E009][E026] On UE capabilities for cross RAT RLF reporting and inter-RAT MRO related RLF reporting | Ericsson |
| R2-2003089 | [E023] On including beamFailureRecoveryFailure in SCG failure information messages | Ericsson |
| R2-2003090 | [E023] On including beamFailureRecoveryFailure in SCGFailureInformationNR message | Ericsson |
| R2-2003092 | [E028] On SON-MDT related UE capabilities addition | Ericsson |
| R2-2003119 | Consideration on Adding the Re-connection Attempt Cell Identity | CATT, CMCC |
| R2-2003162 | N016 on missing RA-report availability indicator | Nokia, Nokia Shanghai Bell |
| R2-2003163 | N017 RA-report also for failed RA procedures | Nokia, Nokia Shanghai Bell |
| R2-2003164 | N018 Actions upon successful completion of random-access procedure | Nokia, Nokia Shanghai Bell |
| R2-2003576 | Minor issues on SON | Huawei, HiSilicon |
| R2-2003784 | Consideration on Adding the Re-connection Attempt Cell Identity | CATT, CMCC |
| R2-2003800 | Summary of AI 6.12.4 SON | Ericsson |
| R2-2004004 | [AT109bis-e][802] Open issues on SON (Ericsson) | Ericsson |
| 6.13.1 | General | |
| R2-2003009 | 4-step RA type description | Nokia (rapporteur), Nokia Shanghai Bell, ZTE |
| R2-2004164 | Reply LS on the starting point of MsgB window (R1-2002794; contact: ZTE) | RAN1 |
| R2-2004165 | Reply LS on the support of 2-step CFRA (R1-2002795; contact: ZTE) | RAN1 |
| R2-2004167 | LS Response on preamble-to-PRU mapping for 2-step CFRA (R1-2002901; contact: Ericsson) | RAN1 |
| 6.13.2 | User plan aspects | |
| R2-2002585 | Remaining Issues on Resource Selection in 2-setp RACH | vivo |
| R2-2002668 | msgB-RNTI ambiguity for CFRA and CBRA of 2-Step RACH | Sony |
| R2-2002840 | Remaining issues of 2-step RACH | OPPO |
| R2-2002965 | Updates to MAC spec for 2-step RACH | ZTE (CR editor), Nokia, Samsung, Vivo |
| R2-2003007 | Discussion on remaining issues of 2-step RA | Huawei, HiSilicon |
| R2-2003356 | Handling invalid POs for MsgA transmissions | Ericsson |
| R2-2003357 | Change LCID to eLCID for Absolute Timing Advance Command | Ericsson |
| R2-2003362 | Correction of Handling of invalid POs for MsgA transmissions | Ericsson |
| R2-2003666 | Further clarifications on parameters for Random Access procedure | LG Electronics |
| R2-2003960 | UP Tdoc summary for 2-step RACH | Rapporteur (ZTE) |
| R2-2003962 | Updates to MAC spec for 2-step RACH | ZTE (CR editor), Nokia, Samsung, Vivo |
| 6.13.3 | RRC stage-3 related aspects | |
| R2-2002556 | Issues - 2 step RA | Samsung Electronics Co., Ltd |
| R2-2002878 | RAN2 related UE capability for 2-step RACH | Intel Corporation |
| R2-2003255 | Remaining issue on 2-step CFRA | Qualcomm Incorporated |
| R2-2003649 | Correction on 2-step RACH configurations in RRC | ASUSTeK |
| R2-2003961 | draft LS to RAN1 on agreements related to 2-step RACH | ZTE |
| R2-2003970 | LS to RAN1 on agreements related to 2-step RACH | RAN2 |
| R2-2004101 | RRC ASN.1 open issues | ericsson |
| R2-2004173 | [AT109bis-e][507][2s RA] CP and ASN.1 Issues(Ericsson) Phase 2 | Ericsson |
| R2-2004188 | LS to RAN1 on agreements related to 2-step RACH | RAN2 |
| R2-2004236 | Corrections for 2-step Random Access Type | Ericsson |
| R2-2004288 | Corrections for 2-step Random Access Type | Ericsson |
| 6.15.1 | Organisational | |
| R2-2002510 | Reply LS on clarification of CLI resource configuration (R1-2001319; contact: Lenovo) | RAN1 |
| R2-2002511 | LS on CLI measurement and reporting (R1-2001320; contact: LGE) | RAN1 |
| R2-2002528 | Reply LS on CLI measurement capability (R4-2002221; contact: Huawei) | RAN4 |
| R2-2003365 | CLI Featurre overview - Additional changes | Nokia Solutions & Networks (I) |
| 6.15.2 | Remaining open issues | |
| R2-2002885 | Additional frequency information for CLI measurements | Samsung |
| R2-2002909 | Additional configuration for CLI resources | LG Electronics Inc. |
| R2-2002911 | CR on additional configuration for CLI resources | LG Electronics Inc. |
| R2-2003380 | Remaining issues for RIM/CLI | Ericsson |
| R2-2004240 | CR on additional configuration for CLI resources | LG Electronics Inc. |
| R2-2004241 | Report on CLI specific RILs | LGE |
| 6.16.1 | Organisational | |
| R2-2002883 | Miscellaneous corrections on eMIMO | Samsung |
| R2-2003901 | Miscellaneous corrections on eMIMO | Samsung |
| R2-2003911 | Miscellaneous corrections on eMIMO | Samsung |
| R2-2004251 | LS reply on eMIMO RRC parameters (R1-2002798; contact: Ericsson) | RAN1 |
| 6.16.2 | RRC open issues | |
| R2-2002870 | Correction on the number of CORESETs per BWP (RIL v101) | vivo |
| R2-2002871 | Correction on RLM RS configuration (RIL v102) | vivo |
| R2-2003181 | [Post109e#34][EMIMO] RRC Open Issues (Ericsson) | Ericsson |
| R2-2003710 | Correction on Multi-DCI based multi-TRP transmission for eMBB | Huawei, HiSilicon |
| R2-2003711 | Corrections on multi-TRP transmission for URLLC | Huawei, HiSilicon |
| R2-2003892 | Offline discussion 102: eMIMO RRC aspects - first round | Ericsson (Rapporteur) |
| R2-2003897 | eMIMO corrections | Ericsson |
| R2-2003898 | [AT109bis-e][102][EMIMO] RRC aspects (Ericsson) | Ericsson (Email discussion rapporteur) |
| R2-2003899 | eMIMO corrections | Ericsson |
| R2-2003910 | eMIMO corrections | Ericsson |
| 6.16.3 | Other open issues | |
| R2-2002557 | Issues - SCell BFR | Samsung Electronics Co., Ltd |
| R2-2002605 | Discussion on pending BFR SR upon SCell deactivation | Sharp, Samsung |
| R2-2002795 | Report of [Post109e#17][EMIMO] BFR MAC CE for BFR on SpCell | Apple |
| R2-2002796 | Timer based BFR MAC CE Transmission | Apple, Nokia, Nokia Shanghai Bell |
| R2-2002872 | Discussion on the SCell BFD on the deactivated SCell | vivo |
| R2-2002873 | Correction on the SP SRS ActivationDeactivation MAC CE | vivo |
| R2-2002882 | Considerations on the number of pathloss RSs indicated by MAC CE | Samsung |
| R2-2002926 | SR configuration for SCell beam failure recovery | Lenovo, Motorola Mobility |
| R2-2002954 | CC list-based SRS Activation/Deactivation MAC CE design | OPPO |
| R2-2002957 | [Post109e#17] Identified other open issues | Fujitsu |
| R2-2003034 | Consideration on SpCell BFR MAC CE | LG Electronics Inc. |
| R2-2003051 | Draft CR on bitmap length determination for BFR MAC CE | Nokia, Nokia Shanghai Bell, Apple |
| R2-2003052 | Draft CR on Corrections for SCell BFR procedure | Nokia, Nokia Shanghai Bell, Apple |
| R2-2003252 | Correction on new DL MIMO MAC CE | Qualcomm Incorporated |
| R2-2003253 | Cancellation the pending BFR SR | Qualcomm Incorporated |
| R2-2003345 | On DCI format 1_2 applicability with NR eMIMO | Ericsson |
| R2-2003358 | Change LCID to eLCID for MIMO MAC CEs | Ericsson |
| R2-2003588 | Remaining issue on aborting of ongoing RACH triggred by SR | ZTE, Sanechips |
| R2-2003589 | Remaining issues on BFR on SCell | ZTE, Sanechips |
| R2-2003618 | Discussion on open issues on BFR MAC CE | Google Inc. |
| R2-2003650 | Remaining issues regarding cancellation of triggered BFRs for SCell | ASUSTeK |
| R2-2003651 | Discussion on completion of RA procedure for SCell beam failure recovery | ASUSTeK |
| R2-2003663 | Clarification on scheduling request for SCell beam failure recovery | Google Inc. |
| R2-2003712 | Remaining issues on SCell BFR | Huawei, HiSilicon |
| R2-2003713 | BFR MAC CE for SpCell | Huawei, HiSilicon |
| R2-2003795 | Summary of proposed corrections_AI_6_16_3 | Samsung Electronics Co., Ltd |
| R2-2003833 | Alignment of SR clause | Ericsson, Samsung |
| R2-2003891 | Offline discussion 101: eMIMO MAC corrections - first round | Samsung |
| R2-2003893 | Offline discussion 103: BFR on SpCell - first round | Apple |
| R2-2003894 | Offline discussion 104: Timer based BFR MAC CE Transmission | Nokia |
| R2-2003900 | Offline discussion 101: eMIMO MAC corrections - second round | Samsung |
| R2-2003902 | Offline discussion 103: BFR on SpCell - second round | Apple |
| R2-2003903 | Offline discussion 104: Timer based BFR MAC CE Transmission - second round | Nokia |
| 6.18.1 | Organisational | |
| R2-2002502 | Reply LS on sending CAG ID (C1-201027; contact: Ericsson) | CT1 |
| R2-2003870 | Reply LS on manual CAG selection | RAN2 |
| R2-2004177 | Reply LS on Manual CAG ID selection and granularity of UAC parameters for PNI-NPNs (C1-202846; contact: Huawei) | CT1 |
| R2-2004178 | LS on manual CAG selection (C1-202927; contact: Nokia) | CT1 |
| 6.18.2 | RRC open issues | |
| R2-2002658 | Finalization of the support of Non-Public Networks | Nokia (Rapporteur) |
| R2-2002659 | Report from email discussion [Post109e#18][PRN] Remaining open issues | Nokia (Rapporteur) |
| R2-2002666 | Blacklist/whitelist for PCI range signaling and stage-3 details | Sony |
| R2-2002745 | Further consideration on the PCI range | ZTE Corporation, Sanechips |
| R2-2002746 | Further consideration on the cell reselection for the licensed spectrum | ZTE Corporation, Sanechips |
| R2-2003319 | Cell reselection restriction for SNPN and CAG | Intel Corporation |
| R2-2003501 | Remaining Issues the PCI Range | CMCC |
| R2-2003507 | Remaining issues on access and mobility control for NPN | CMCC |
| R2-2003529 | Discussion on the ANR for NPN | vivo |
| R2-2003604 | Emergency sessions on CAG-only cell for non-CAG capable R16 UEs | LG Electronics France |
| R2-2003606 | On SNPN Cell Reselection in Licensed Bands | NEC Telecom MODUS Ltd. |
| R2-2003895 | Offline discussion 105: PRN open issues - first round | Nokia (Rapporteur) |
| R2-2003896 | Offline discussion 105: PRN open issues - second round | Nokia (Rapporteur) |
| R2-2003907 | (Offline discussion 105: PRN open issues - third round | Nokia (Rapporteur) |
| 6.18.3 | Other open issues | |
| R2-2002593 | Cell selection and reselection for NPN | Ericsson |
| R2-2002594 | Manual selection of PNI NPNs when CAG is broadcast | Ericsson |
| R2-2002734 | Discussion on HRNNs Reporting Issue | CATT |
| R2-2002736 | Discussion on UE Behavior in Licensed Band with Non-CAG Member Cell | CATT |
| R2-2003259 | Consideration of HRNN and UAC in PRN | China Telecom |
| R2-2003261 | Remaining issues discussion on NPN | China Telecom |
| R2-2003394 | Emergency call support on CAG-only cells | Qualcomm Incorporated |
| R2-2003421 | Running CR to TS 38.304 for PRN | Qualcomm Incorporated |
| R2-2003474 | Discussion on manual CAG selection | Huawei, HiSilicon, China Telecom |
| R2-2003475 | Discussion on mechanisms for the network to control manual NPN selection | Huawei, HiSilicon, China Telecom |
| R2-2003558 | Some Issues related to 38.304 | Samsung R&D Institute India |
| R2-2003605 | Intra-frequency reselection upon selecting non-suitable SNPN cell | LG Electronics France |
| R2-2003608 | Remaining issues related to Manual CAG Selection | Samsung R&D Institute India |
| R2-2003908 | Running CR to TS 38.304 for PRN | Qualcomm Incorporated |
| R2-2003912 | Offline discussion 107: PRN 38.304 CR | Qualcomm Incorporated (Rapporteur) |
| 6.19 | Other NR Rel-16 WIs/SIs | |
| R2-2002504 | LS on MO exception data (C4-201003; contact: CATT) | CT4 |
| R2-2002526 | LS on FDD band capability signalling for uplink sharing (R4-1916180; contact: Nokia) | RAN4 |
| R2-2002527 | LS on MPE enhancements (R4-1916183; contact: Qualcomm) | RAN4 |
| R2-2002531 | LS on UE Tx switching period delay and DL interruption (R4-2002816; contact: Apple) | RAN4 |
| R2-2002532 | LS on the misalignment in P-bit between single entry and multi-entry PHR (R4-2002820; contact: OPPO) | RAN4 |
| R2-2002533 | LS to RAN2 on introduction of channel bandwidth combination set to asymmetric channel bandwidths (R4-2002852; contact: Huawei) | RAN4 |
| R2-2002534 | LS on MPE enhancements (R4-2002916; contact: Nokia) | RAN4 |
| R2-2002537 | LS on the support for ECN in 5GS (S2-1912765; contact: Qualcomm) | SA2 |
| R2-2002538 | Reply LS on Enhancements to QoS Handling for V2X Communication Over Uu Reference Point (S2-2001675; contact: Nokia) | SA2 |
| R2-2002543 | Reply LS on Support for ECN in 5GS (S4-200298; contact: Qualcomm) | SA4 |
| R2-2002575 | ULSUP applicability to FDD bands | Qualcomm Incorporated |
| R2-2002576 | Introduction of UE capability for ULSUP with FDD band | Qualcomm Incorporated, Nokia, OPPO |
| R2-2002577 | Introduction of UE capability for ULSUP with FDD band | Qualcomm Incorporated, Nokia, OPPO |
| R2-2002580 | [DRAFT] Response LS on the support for ECN in 5GS | Qualcomm Incorporated |
| R2-2002616 | P bit in Single Entry PHR MAC CE | Samsung |
| R2-2002631 | Introduction of asymmetric BW BCS 1 | OPPO |
| R2-2002632 | Introduction of asymmetric BW BCS 1 | OPPO |
| R2-2002633 | Introduction of asymmetric BW BCS 0 | OPPO |
| R2-2002634 | Introduction of asymmetric BW BCS 0 | OPPO |
| R2-2002676 | Discussion on P indcatior in single entry PHR | OPPO |
| R2-2002684 | UE FR2 MPE enhancements and solutions | Nokia, Nokia Shanghai Bell |
| R2-2002685 | Introduction of FR2 MPE P-MPR reporting | Nokia, Nokia Shanghai Bell |
| R2-2002686 | Introduction of FR2 MPE P-MPR reporting | Nokia, Nokia Shanghai Bell |
| R2-2002687 | Introduction of FR2 MPE P-MPR reporting | Nokia, Nokia Shanghai Bell |
| R2-2002688 | Introduction of FR2 MPE P-MPR reporting | Nokia, Nokia Shanghai Bell |
| R2-2002689 | Clarifications on UL Tx switching | Nokia, Nokia Shanghai Bell |
| R2-2002738 | Temporary Boost | Nokia, Nokia Shanghai Bell |
| R2-2002739 | LS on Temporary Boost | Nokia |
| R2-2002805 | On Tx switching | Apple |
| R2-2002806 | On Tx switching | Apple |
| R2-2002820 | P-MPR Reporting | Apple |
| R2-2003010 | P bit for Single Entry PHR | Nokia, Nokia Shanghai Bell, Apple, Ericsson, Lenovo, NTT DOCOMO, INC. |
| R2-2003264 | Report of email discussion [Post109e#33][R16 Other] UL TX Switching-NR_FR1 | ChinaTelecom |
| R2-2003265 | 38306CR for UE capability of supporting UL Tx switching | ChinaTelecom |
| R2-2003266 | 38331CR for UE capability and RRC configuration of supporting UL Tx switching | ChinaTelecom |
| R2-2003426 | Correction to description of ECN | Ericsson |
| R2-2003427 | Correction to description of ECN | Ericsson |
| R2-2003446 | Discussion on UL sharing for variable-duplex FDD bands | Huawei, HiSilicon |
| R2-2003448 | On the support of EN-DC FDD+TDD HPUE | Huawei, HiSilicon |
| R2-2003449 | support of EN-DC FDD+TDD HPUE | Huawei, HiSilicon |
| R2-2003450 | support of EN-DC FDD+TDD HPUE | Huawei, HiSilicon |
| R2-2003469 | CR on introduction of BCS to asymmetric channel bandwidths (38.331) | Huawei, HiSilicon, Telus |
| R2-2003470 | CR on introduction of BCS to asymmetric channel bandwidths (38.306) | Huawei, HiSilicon, Telus |
| R2-2003508 | 38.331 CR on introduction of RRC parameters and UE capabilities for Rel-16 NR HST | CMCC, Huawei, HiSilicon, CATT |
| R2-2003509 | 38.306 CR on introduction of UE capabilities for Rel-16 NR HST | CMCC, Huawei, HiSilicon, CATT |
| R2-2003823 | Report of email discussion [Post109e#33][R16 Other] UL TX Switching-NR_FR1 | ChinaTelecom |
| R2-2004124 | Email report of [AT109bis-e][042][NR16 Other] P bit for Single Entry PHR (OPPO | OPPO |
| R2-2004137 | 38331CR for UE capability and RRC configuration of supporting UL Tx switching | ChinaTelecom |
| R2-2004181 | 38.331 CR on introduction of RRC parameters and UE capabilities for Rel-16 NR HST | CMCC, Huawei, HiSilicon, CATT, Ericsson |
| R2-2004182 | 38.306 CR on introduction of UE capabilities for Rel-16 NR HST | CMCC, Huawei, HiSilicon, CATT, Ericsson |
| R2-2004201 | Report of [AT109bis-e][045][NR16 Other] UL TX Switching-NR_FR1 | China Telecom |
| R2-2004205 | [DRAFT] Response LS on the support for ECN in 5GS | Qualcomm Incorporated |
| R2-2004210 | CR on introduction of BCS to asymmetric channel bandwidths (38.306) | Huawei, HiSilicon, Telus |
| R2-2004211 | Draft reply LS on asymmetric channel bandwidths | Huawei |
| R2-2004214 | UE capability for single entry PHR with P bit | OPPO, Ericsson, MediaTek Inc., Nokia, Nokia Shanghai Bell, vivo, ZTE, Xiaomi |
| R2-2004215 | UE capability for single entry PHR with P bit | OPPO, Ericsson, MediaTek Inc., Nokia, Nokia Shanghai Bell, vivo, ZTE, Xiaomi |
| R2-2004222 | Reply LS on MO exception data (S2-2003504; contact: Qualcomm) | SA2 |
| R2-2004238 | Report for [AT109bis-e][047][NR16 Other] NR HST | CMCC |
| R2-2004255 | Reply LS on UE Tx switching period delay and DL interruption (R1-2002960; contact: Apple) | RAN1 |
| R2-2004256 | Response LS on the support for ECN in 5GS | RAN2 |
| R2-2004268 | Reply LS on asymmetric channel bandwidths | RAN2 |
| R2-2004284 | Response LS on the support for ECN in 5GS | RAN2 |
| 6.20 | NR TEI16 enhancements | |
| R2-2004218 | Reply LS on support for eCall over NR (S2-2003308; contact: Qualcomm) | SA2 |
| 6.20.1.1 | Open / ongoing proposals | |
| R2-2002535 | LS on 5G indicator (RP-193265; contact: Intel) | RAN |
| R2-2002560 | Corrections to PRACH prioritization procedure for MPS and MCS | Samsung Electronics Co., Ltd |
| R2-2002561 | Corrections to PRACH prioritization procedure for MPS and MCS | Samsung Electronics Co., Ltd |
| R2-2002581 | Correction on establishment cause value upon enhanced EPS voice fallback | Qualcomm Incorporated |
| R2-2002660 | A RAN Based Solution for the 5G Indicator | VODAFONE |
| R2-2002677 | additional SSB-ToMeasure for smtc2-LP | OPPO, ZTE, CMCC |
| R2-2002770 | Remaining issue on NR NeedForGap signaling | MediaTek Inc. |
| R2-2002781 | Introduction of NeedForGap capability for NR measurement - 36.331 | MediaTek Inc. |
| R2-2002782 | Introduction of NeedForGap capability for NR measurement - 36.306 | MediaTek Inc. |
| R2-2002783 | Introduction of NeedForGap capability for NR measurement - 38.300 | MediaTek Inc. |
| R2-2002784 | Introduction of NeedForGap capability for NR measurement - 38.331 | MediaTek Inc. |
| R2-2002785 | Introduction of NeedForGap capability for NR measurement - 38.306 | MediaTek Inc. |
| R2-2002811 | Discussion on NeedForGap | Apple |
| R2-2002812 | Draft LS to RAN4 on NeedForGap | Apple |
| R2-2002958 | SR_COUNTER initialization due to RRC reconfiguration | Fujitsu, LG Electronics Inc. |
| R2-2002969 | Upper layer indication | ZTE Corporation, Sanechips |
| R2-2003109 | Missing reportAddNeighMeas in periodic measurement reporting | Nokia, Nokia Shanghai Bell |
| R2-2003142 | Transfer of unicast RS observations with GNSS integer ambiguity level information | Ericsson |
| R2-2003416 | Introduction of bandlist for ENDC for 5G indicator | HUAWEI, HiSilicon, Telefonica, Telecom Italia S.p.A., Samsung |
| R2-2003417 | Introduction of bandlist for ENDC for 5G indicator | Huawei, HiSilicon, Telefonica, Telecom Italia S.p.A., Samsung |
| R2-2003418 | Introduction in new SIB of bandlist for ENDC for 5G indicator | Huawei, HiSilicon, BT, Samsung |
| R2-2003419 | Introduction in new SIB of bandlist for ENDC for 5G indicator | Huawei, HiSilicon, BT, Samsung |
| R2-2003420 | EN-DC bandlist for 5G indicator | Huawei, HiSilicon, BT, Telefonica, Telecom Italia S.p.A., Samsung |
| R2-2003467 | 36.331 CR for addressing overheating issue in (NG)EN-DC | Huawei, Huawei Device, Apple, CATT |
| R2-2003468 | 38.331 CR for addressing overheating issue in (NG)EN-DC | Huawei, Huawei Device, Apple, CATT |
| R2-2003490 | Further consideration on EN-DC cell reselection | CMCC,SoftBank, Ericsson, Huawei, ZTE, CATT, vivo, OPPO, Xiaomi |
| R2-2003491 | 36.331 CR to introduce alternative cell reselection priority for EN-DC | CMCC, SoftBank, Ericsson, Huawei, ZTE, CATT, vivo |
| R2-2003492 | 36.304 CR to introduce alternative cell reselection priority for EN-DC | CMCC, SoftBank, Ericsson, Huawei, ZTE, CATT, vivo, OPPO |
| R2-2003493 | 36.306 CR to introduce alternative cell reselection priority for EN-DC | CMCC, SoftBank, Ericsson, Huawei, ZTE, CATT, vivo, OPPO |
| R2-2003494 | 38.331 CR to introduce alternative cell reselection priority for SA | CMCC, Ericsson, SoftBank, vivo |
| R2-2003495 | 38.304 CR to introduce alternative cell reselection priority for SA | CMCC, Ericsson, SoftBank, vivo |
| R2-2003496 | 38.306 CR to introduce alternative cell reselection priority for SA | CMCC, Ericsson, SoftBank, vivo |
| R2-2003723 | Discussion on order of two random access procedures in NR to EN-DC | Samsung Electronics Co., Ltd |
| R2-2003724 | Further discussion on EN-DC cell reselection | Samsung Electronics Co., Ltd |
| R2-2003733 | CR on separate cell reselection priority in EN-DC cell reselection in 36.331 | Samsung Electronics Co., Ltd |
| R2-2003739 | CR on separate cell reselection priority in EN-DC cell reselection in 38.331 | Samsung Electronics Co., Ltd |
| R2-2003754 | Correction on order of two random access procedures in NR to EN-DC HO | Samsung Electronics Co., Ltd |
| R2-2003828 | Discussion on NeedForGap | Apple |
| R2-2003883 | LS on NeedForGap capability | MediaTek |
| R2-2004159 | Summary of [AT109bis-e][049][TEI16] Need for Gap (Mediatek) | MediaTek |
| R2-2004160 | Introduction of NeedForGap capability for NR measurement - 38.300 | MediaTek Inc. |
| R2-2004161 | Introduction of NeedForGap capability for NR measurement - 38.331 | MediaTek Inc. |
| R2-2004193 | Report from email discussion [AT109bis-e][048][TEI16] on 5G indicator | Intel Corporation |
| R2-2004212 | Summary for [AT109bis-e][050][TEI16] Overheating | Huawei |
| R2-2004237 | Report for [AT109bis-e][051][TEI16] EN-DC cell reselection | CMCC |
| R2-2004264 | upperLayerIndication enhancements | Huawei, HiSilicon, BT, Samsung |
| 6.20.1.3 | New proposals | |
| R2-2002640 | CR to 38.331 on missing freqBandIndicator in NR redirection | Qualcomm Incorporated |
| R2-2002641 | CR to 36.331 on missing freqBandIndicator in NR redirection | Qualcomm Incorporated |
| R2-2002764 | Clarification on providing network specific uac-AccessCategory1-SelectionAssistanceInfo | ZTE Corporation, Sanechips |
| R2-2002765 | CR on providing network specific uac-AccessCategory1-SelectionAssistanceInfo | ZTE Corporation, Sanechips |
| R2-2002792 | SRB only connection enhancement for PDU session change | CATT,Huawei, HiSilicon |
| R2-2002793 | SRB only connection ehancement option 1 | CATT,Huawei, HiSilicon |
| R2-2002794 | SRB only connection ehancement option 2 | CATT |
| R2-2002813 | UE Information for 0-PDCCH | Apple |
| R2-2002884 | Additional UE capability filtering to limit the total number of carriers in NR | Samsung |
| R2-2002927 | On combined RRC procedures | Nokia, Nokia Shanghai Bell, Ericsson |
| R2-2002928 | RRC processing delays for combined procedures | Nokia, Nokia Shanghai Bell, Ericsson |
| R2-2002970 | Updates to reestablishment procedure | ZTE Corporation, Sanechips, Intel Corporation, CATT |
| R2-2003072 | Measurement priority handling in NR | Ericsson |
| R2-2003476 | On the support of NG-based (i.e. via CN) handover using CGI report | Huawei, HiSilicon |
| R2-2003531 | Signalling enhancement for Inactive state | CATT |
| R2-2003532 | Bearer type negotiation | CATT |
| 6.20.2.1 | Open / ongoing proposals | |
| R2-2002740 | LCP Mapping Restrictions | Nokia, Deutsche Telekom, Ericsson, Fujitsu, Nokia Shanghai Bell, NTT DOCOMO INC., T-Mobile |
| R2-2002741 | Dynamic LCP Mapping Restrictions | Nokia, Deutsche Telekom, Fujitsu, Nokia Shanghai Bell, NTT DOCOMO INC., T-Mobile |
| R2-2002835 | Cell restriction for CA duplication | OPPO |
| R2-2002836 | Further considerations on secondary DRX group | OPPO |
| R2-2002876 | Views on TEI for Secondary DRX Group | vivo |
| R2-2003103 | Discussion on PDCCH-WUS works with Dual DRX | Xiaomi Communications |
| R2-2003115 | Further details on Secondary DRX group | NEC |
| R2-2003284 | Introduction of secondary DRX group | Ericsson, Qualcomm, Samsung, InterDigital, Deutsche Telekom, Verizon |
| R2-2003285 | Introduction of secondary DRX group | Ericsson, Qualcomm, Samsung, InterDigital, Deutsche Telekom, Verizon |
| R2-2003286 | Introduction of secondary DRX group | Ericsson, Qualcomm, Samsung, InterDigital, Deutsche Telekom, Verizon |
| R2-2003287 | Introduction of secondary DRX group | Ericsson, Qualcomm, Samsung, InterDigital, Deutsche Telekom, Verizon |
| R2-2004114 | Offline 053 on LCP Mapping Restrictions | Nokia |
| R2-2004234 | LS response on secondary DRX group (R1-2002961; contact: Ericsson) | RAN1 |
| 6.20.2.3 | New proposals | |
| R2-2002667 | RNTI ambiguity for CFRA and CBRA of 4-Step RACH | Sony |
| R2-2002742 | QoS Flow Handling | Nokia, Nokia Shanghai Bell |
| R2-2002743 | MDBV Enforcement | Nokia, InterDigital, Nokia Shanghai Bell |
| R2-2002880 | Unnecessary deciphering for duplicated PDUs | Samsung |
| R2-2002912 | CR on PDCP security issue about duplicate detection | Samsung, LG Electronics Inc., Nokia, Nokia Shanghai Bell, LG Uplus, Deutsche Telekom |
| R2-2002937 | ON Duration adaptation | LG Electronics Inc., LG Uplus, Vivo |
| R2-2002998 | Retransmission of an RLC SDU with a poll after discard procedure | LG Electronics Inc., Ericsson, NTT Docomo, LG Uplus, Sharp |
| R2-2003053 | CFRA resource handling for BFR upon TAT expiry | Nokia, Nokia Shanghai Bell, Apple, ASUSTek |
| R2-2003223 | Adaptation of QoS Flow to DRB Mapping for MDBV Enforcement | Futurewei |
| R2-2003403 | Maximum Number of DRBs and RLC entities | Nokia, Nokia Shanghai Bell |
| R2-2003611 | Stopping ra-ResponseWindow for contention-free BFR | Huawei, HiSilicon, China Unicom |
| R2-2003825 | CR on PDCP security issue about duplicate detection | Samsung, LG Electronics Inc., Nokia, Nokia Shanghai Bell, LG Uplus, Deutsche Telekom, NTT DOCOMO |
| 6.20.3.1 | Open / ongoing proposals | |
| R2-2002595 | Introduction of enhanced support for dynamic spectrum sharing | Ericsson |
| R2-2002596 | Introduction of enhanced support for dynamic spectrum sharing | Ericsson |
| R2-2003465 | Discussion on release for under-reporting CSI-RS capabilities | Huawei, HiSilicon, China Telecom, CMCC, China Unicom |
| R2-2003466 | Signalling design for under-reporting CSI-RS capabilities | Huawei, HiSilicon, China Telecom, CMCC, China Unicom |
| R2-2003564 | Discussion on eCall over IMS for NR | Huawei, HiSilicon |
| R2-2003565 | Introduction of eCall over IMS for NR | Huawei, HiSilicon |
| R2-2003566 | Introduction of eCall over IMS for NR | Huawei, HiSilicon |
| R2-2003567 | Introduction of eCall over IMS for NR | Huawei, HiSilicon |
| R2-2003568 | Draft reply LS on support for eCall over NR | Huawei |
| R2-2003593 | Remaining issues on the ambiguity in calculation of RA-RNTI | ZTE, Sanechips |
| R2-2004185 | Summary of [AT109bis-e][055][TEI16] eCall over NR | Huawei |
| R2-2004186 | Introduction of eCall over IMS for NR | Huawei, HiSilicon |
| R2-2004253 | Reply LS on CSI-RS capabilities (FG 2-33/36/40/41/43) (R1-2002900; contact: NTT DOCOMO) | RAN1 |
| 6.21 | On demand SI in connected | |
| R2-2002723 | Remaining issues for on-demand system information | MediaTek Inc. |
| R2-2002766 | Repetition of on demand SI request following UE mobility | ZTE Corporation, Sanechips |
| R2-2003070 | Discussion on on-demand SI in RRC-CONNECTED | Huawei, HiSilicon |
| R2-2003123 | Requesting SIBs not supported in the cell | Lenovo, Motorola Mobility |
| R2-2003203 | Feature summary for on-demand SIB in CONNECTED | Ericsson |
| R2-2003204 | Summary of [Post109e#29][OdSIBconn] Open Issues | Ericsson |
| R2-2003205 | Introduction of on-demand SIB in CONNECTED with positioning | Ericsson |
| R2-2003543 | Remaining Issues of On Demand SI in RRC Connected | Samsung R&D Institute India |
| R2-2003582 | Necessity of prohibt timer for SI request in connected mode. | LG Electronics France |
| R2-2003787 | Introduction of on-demand SIB in CONNECTED with positioning | Ericsson |
| R2-2003836 | Introduction of on-demand SIB in CONNECTED with positioning | Ericsson |
| R2-2003840 | Summary of [AT109bis-e][056][OdSIBconn] On demand SI Open issue | Ericsson |
| R2-2003876 | Introduction of on-demand SIB in CONNECTED with positioning | Ericsson |
| R2-2004245 | [AT109bis-e][056][OdSIBconn] On demand SI Open issue_Phase2 | Ericsson |
| R2-2004286 | [Post109bis-e][OdSIBconn] On demand SI Open issue | Ericsson |
| 6.22.1 | Organizational | |
| R2-2003612 | Running RRC CR by capturing updated L1 parameters for NR eURLLC | Huawei, HiSilicon |
| R2-2003613 | Running CR for UE feature list for NR eURLLC | Huawei, HiSilicon |
| R2-2003614 | Running CR for UE feature list for NR eURLLC | Huawei, HiSilicon |
| 6.22.2 | Control Plane | |
| R2-2003615 | Mapping between PUCCH resource ID and PUCCH Config for eURLLC | Huawei, HiSilicon |
| R2-2003667 | Draft 38.331 CR on L1 parameters | LG Electronics |
| R2-2004145 | Summary of [AT109bis-e][057][URLLC] RRC L1 Configuration | Huawei |
| R2-2004146 | Correction to RRC spec for eURLLC | Huawei |
| R2-2004285 | Correction to RRC spec for eURLLC | Huawei |
| 6.22.3 | User Plane | |
| R2-2002714 | on MAC CE design for eURLLC | Ericsson |
| R2-2003616 | Remaining issues of MAC aspects for eURLLC | Huawei, HiSilicon |
| R2-2004147 | Summary of [AT109bis-e][058][URLLC] MAC remaining issues | Huawei |
| R2-2004148 | Correction to MAC spec for eURLLC | Huawei |
| 7.0.1 | ASN.1 review | |
| R2-2003231 | General ASN.1 issues for 36.331 Rel-16 (S001- S006) | Samsung Telecommunications |
| R2-2003234 | ASN.1 Review file (LTE) | Samsung Telecommunications |
| R2-2003235 | LTE Rel-16 ASN.1 Review, Class 0 and Class 1 issues | Samsung Telecommunications |
| R2-2003389 | General ASN.1 issues for 36.331 Rel-16 (S001- S006) | Samsung Telecommunications |
| R2-2003392 | ASN.1 Review file (LTE) | Samsung Telecommunications |
| R2-2003393 | LTE Rel-16 ASN.1 Review, Class 0 and Class 1 issues | Samsung Telecommunications |
| R2-2003827 | ASN.1 Review RIL (LTE) | Samsung Telecommunications |
| R2-2003843 | [AT109e][066][R16] R16 LTE RRC coordination (Samsung) | Samsung |
| 7.0.2 | Features and UE capabilities | |
| R2-2002550 | LS on Rel-16 RAN1 UE features lists for LTE (R1-2001486; contact: NTT DOCOMO) | RAN1 |
| 7.1.1 | Organisational | |
| R2-2002503 | Reply LS on Mobile-terminated Early Data Transmission (C1-201062; contact: Ericsson) | CT1 |
| R2-2002849 | Miscellaneous Rel-16 eMTC corrections | Qualcomm Incorporated |
| R2-2003351 | Minor corrections and resolving Editor's Notes in TS36321 | Ericsson |
| R2-2003918 | Miscellaneous corrections to Rel-16 eMTC enhancements | Intel Corporation |
| R2-2003920 | Corrections to WUS group for eMTC | Nokia |
| R2-2003922 | Corrections to MAC for Rel-16 eMTC | Ericsson |
| R2-2003923 | Miscellaneous Rel-16 eMTC corrections | Qualcomm Incorporated |
| R2-2004223 | LS on SA WG2 status of MT-EDT in Rel-16 (S2-2003505; contact: Qualcomm) | SA2 |
| 7.1.3 | Scheduling multiple DL/UL transport blocks | |
| R2-2003352 | drx-InactivityTimer for LTE-M when scheduling multiple TBs | Ericsson |
| 7.1.4 | Quality report in Msg3 | |
| R2-2003134 | Solution for the short quality reporting for eMTC | Ericsson |
| R2-2003182 | Msg3 Quality report way forward on open issue | Qualcomm Incorporated, BlackBerry, LG Electronics, Nokia, Nokia Shanghai Bell, Sanechips, Sequans Communications, Sierra Wireless, Sony, Thales, ZTE |
| R2-2003183 | Introduce 2-bit CQI based on Solution 1 | Qualcomm Incorporated |
| R2-2003343 | TP for 2-bit Quality report in Msg3 | Huawei, HiSilicon |
| R2-2003785 | Summary of Channel Quality report open issues | Huawei |
| R2-2003925 | Summary of Channel Quality report open issues | Huawei, HiSilicon |
| 7.1.6 | Improvements for non-BL UEs | |
| R2-2002879 | Non-BL UE in enhanced coverage mode in “normal” cell | Intel Corporation |
| R2-2003344 | Enhancements to idle mode mobility for non-BL UEs | Huawei, HiSilicon |
| R2-2003353 | S-Criterion interpretation for non-BL UEs | Ericsson |
| R2-2003791 | Summary of AI 7.1.6 Improvements for non-BL UEs | Ericsson |
| R2-2003926 | Report on [AT109bis-e][411][eMTC] Idle mode mobility for non-BL UEs - Open issues | Ericsson |
| 7.1.7 | Stand-alone deployment | |
| R2-2003354 | Remaining issues for LTE-M standalone deployment | Ericsson |
| R2-2003771 | Finalization of TP for cell selection at standalone cell | Nokia, Nokia Shanghai Bell |
| R2-2003792 | Summary of AI 7.1.7 Standalone operation | Ericsson |
| R2-2003927 | Report on [AT109bis-e][412][eMTC] Standalone deployment – open issues | Ericsson |
| 7.1.8 | Mobility Enhancements | |
| R2-2003138 | Introduction of RSS Configurations | Ericsson |
| R2-2003141 | Report on Email discussion RSS Configurations | Ericsson |
| R2-2003188 | Permit early implementation of relaxed serving cell measurement | Qualcomm Incorporated |
| R2-2003814 | Addressing FFSs for RSS configuration | ZTE Corporation, Sanechips, Ericsson |
| R2-2003928 | Report for [AT109bis-e][413][eMTC] Mobility enhancements - Open issues (Qualcomm) | Qualcomm |
| 7.1.9 | Coexistence with NR | |
| R2-2003477 | Further discussion on NB-IoT coexistence with NR | ZTE Corporation, Sanechips |
| R2-2003478 | Further discussion on eMTC coexistence with NR | ZTE Corporation, Sanechips |
| R2-2003929 | Report of [AT109bis-e][414][eMTC/NB-IoT]Coexistence with NR-Open issues (ZTE) | ZTE (email discussion rapporteur) |
| R2-2004166 | LS response on NR coexistence (R1-2002899; contact: Qualcomm) | RAN1 |
| 7.1.10 | Connection to 5GC | |
| R2-2002607 | Report for [Post109e#47][eMTC/NB-IoT] Connection to 5GC Open Issues | Qualcomm India Pvt Ltd |
| R2-2002609 | Idle Mode cell reselection based on CN type supported | Qualcomm Incorporated, TurkCell |
| R2-2002610 | Early UE capability retrieval enhancements for eMTC/5GC | Qualcomm India Pvt Ltd |
| R2-2002611 | [Draft] LS on early UE capability retrieval for eMTC connected to both EPC and 5GC | Qualcomm India Pvt Ltd |
| R2-2002929 | Draft reply LS on suspension indication to 5G NAS | Qualcomm India Pvt Ltd |
| R2-2003428 | AS RAI and optimization of release | Ericsson, LG Electronics Inc., Sony, Sierra Wireless, Thales, Lenovo, Motorola Mobility, MediaTek Inc., Turkcell |
| R2-2003430 | LS on AS RAI and optimization of release | Ericsson |
| R2-2003796 | [Pre109bis-e][NBIOT/eMTC] Summary of eMTC/NB-IoT connected to 5GC | Qualcomm |
| R2-2003930 | [AT109bis-e][415][eMTC/NB-IoT] Connection to 5GC - Open issues (Qualcomm) | Qualcomm Inc (summary rapporteur) |
| R2-2003935 | LS on early UE capability retrieval for eMTC | RAN2 |
| R2-2003936 | Draft reply LS on suspension indication to 5G NAS | Qualcomm India Pvt Ltd |
| R2-2003940 | Reply LS on suspension indication to 5G NAS | RAN2 |
| R2-2003942 | Reply LS on suspend indication 5G NAS | RAN2 |
| 7.1.11 | MTC UE capabilities | |
| R2-2003341 | Update to UE capabilities for eMTC | Huawei, HiSilicon |
| R2-2003921 | Update to UE capabilities for eMTC | Huawei, HiSilicon |
| 7.1.12 | ASN.1 review - MTC | |
| R2-2002841 | [Q501] Corrections to resumption of SRB1 in TS 36.331 subclause 5.3.3.3a | Qualcomm Incorporated |
| R2-2003268 | Capture AS context discard when CN type change | ZTE Corporation, Sanechips |
| R2-2003279 | Correction on trigger for MT-EDT | ZTE Corporation, Sanechips |
| R2-2003931 | [AT109bis-e][416][eMTC] ASN.1 review for eMTC | Qualcomm |
| R2-2003932 | [AT109bis-e][417][eMTC] Interworking between Cat M and NR | Qualcomm |
| 7.1.13 | Other | |
| R2-2003185 | Interworking between Cat M and NR | Qualcomm Incorporated |
| R2-2003186 | Draft Reply LS on category M devices and NR | Qualcomm Incorporated |
| R2-2003187 | Calrify interworking between Cat M and NR is not supported. | Qualcomm Incorporated |
| R2-2003934 | Reply LS on category M devices and NR | RAN2 |
| 7.2.1 | Organisational | |
| R2-2002587 | RAN2 agreements for Rel-16 additional enhancements for NB-IoT and MTC | Document Rapporteur (BlackBerry) |
| R2-2003249 | Miscellaneous corrections to TS 36.300 for Rel-16 NB-IoT | Huawei, HiSilicon |
| R2-2003744 | Miscellaneous corrections to 36.331 for Rel-16 NB-IoT | Huawei, HiSilicon |
| R2-2003745 | Miscellaneous corrections to 36.302 for Rel-16 NB-IoT | Huawei, HiSilicon |
| R2-2004039 | Miscellaneous corrections to TS 36.300 for Rel-16 NB-IoT | Huawei, HiSilicon |
| R2-2004040 | Miscellaneous corrections to 36.331 for Rel-16 NB-IoT | Huawei, HiSilicon |
| R2-2004041 | Miscellaneous corrections to 36.302 for Rel-16 NB-IoT | Huawei, HiSilicon |
| R2-2004042 | Introduction of Rel-16 NB-IoT enhancements | Nokia |
| R2-2004043 | Corrections to MAC for Rel-16 NB-IoT | Ericsson |
| R2-2004058 | RAN2 agreements for Rel-16 additional enhancements for NB-IoT and MTC | Document Rapporteur (BlackBerry) |
| R2-2004217 | Reply LS on assistance indication for WUS (S2-2003217; contact: Qualcomm) | SA2 |
| 7.2.2 | UE-group wake-up signal (WUS) | |
| R2-2002671 | On supporting UE group WUS operation with mobility | Sony |
| R2-2003101 | Consideration on WUS paging probability parameter | Lenovo, Motorola Mobility |
| R2-2003102 | Group WUS for mobile UE | Lenovo, Motorola Mobility |
| R2-2003184 | Clarification of WUS resource configuration | Qualcomm Incorporated |
| R2-2003328 | E-mail-Discussion-Summary for Post109e-32 : Finalise TP for TS36.304 for WUS | Nokia, Nokia Shanghai Bell |
| R2-2003329 | Draft TP for TS36.304 | Nokia, Nokia Shanghai Bell |
| R2-2003431 | Report - Email discussion [Post109e#45][NB-IoT/eMTC] WUS open issues | Ericsson |
| R2-2003485 | Formula for WUS group selection | ZTE Corporation, Sanechips |
| R2-2003741 | Signalling changes for GWUS Resource mapping for eMTC | Nokia Solutions & Networks (I) |
| R2-2004045 | Report - Email discussion [AT109bis-e][310][NBIOT eMTC] WUS open issues | Ericsson |
| 7.2.3 | Transmission in preconfigured resources | |
| R2-2003257 | Complete the HARQ process for PUR | ZTE Corporation, Sanechips |
| R2-2003258 | Correction on successful PUR transmission indication | ZTE Corporation, Sanechips |
| R2-2003267 | Correction on TA timer maintenance | ZTE Corporation, Sanechips |
| R2-2003331 | Security Aspects of PUR Configuration for CP | Nokia, Nokia Shanghai Bell |
| R2-2003355 | Moving UL grant handling from MAC to RRC for PUR | Ericsson, Huawei, HiSilicon |
| R2-2003415 | TA validation based on serving cell RSRP change (related to RAN4 LSes) | Sierra Wireless, S.A. |
| R2-2003429 | Configuration and adjustment of repetition number | Sierra Wireless, S.A. |
| R2-2003652 | Remaining issues of D-PUR TA timer in MAC | ASUSTeK |
| R2-2003653 | PUR configuration maintenance during RRC state transition | ASUSTeK |
| R2-2003746 | Report of email discussion [Post109e#46][NBIOT/EMTC] PUR open issues | Huawei |
| R2-2004046 | Report of offline discussion [AT109bis-e][311] on PUR open issues (Huawei) | Huawei |
| R2-2004055 | [DRAFT] LS to SA3 on CP PUR security | Huawei |
| 7.2.4 | NB-IoT Specific | |
| R2-2003131 | To Verify ANR Measurements | Ericsson, Nokia, Nokia Shanghai Bell, ZTE Corporation |
| R2-2003133 | Logging of CE Level for RLF and ANR measurements | Ericsson |
| R2-2003139 | Draft LS to RAN4 on ANR Measurements | Ericsson [To be RAN2] |
| R2-2003247 | SON remaining issues | Huawei, HiSilicon |
| R2-2003291 | Remaining FFSs for SON in NB-IoT | ZTE Corporation, Sanechips |
| R2-2003669 | Report of [Post109e#15][NBIOT] UE specific DRX DRX cycle values | Sequans Communications |
| R2-2003747 | Introduction of UE specific DRX for NB-IoT | Huawei, HiSilicon, MediaTek, CMCC, China Unicom, Ericsson, Lenovo, Motorola Mobility |
| R2-2003748 | [Draft] Reply LS on Rel-16 NB-IoT enhancements | Huawei |
| R2-2003749 | [Draft] LS on UE specific DRX in NB-IoT | Huawei |
| R2-2003780 | Introduction of UE specific DRX for NB-IoT | Huawei, HiSilicon, MediaTek, CMCC, China Unicom, Ericsson, Lenovo, Motorola Mobility, Vodafone |
| R2-2003786 | Summary of SON/ANR open issues | Huawei |
| R2-2003815 | Introduction of UE specific DRX for NB-IoT | Huawei, HiSilicon, MediaTek, CMCC, China Unicom, Ericsson, Lenovo, Motorola Mobility, Vodafone, China Telecom |
| R2-2004047 | Summary of SON/ANR open issues | Session chair |
| R2-2004050 | [Draft] LS on UE specific DRX in NB-IoT | Huawei |
| R2-2004051 | [Draft] Reply LS on Rel-16 NB-IoT enhancements | Huawei |
| R2-2004052 | Report of [AT109bis-e][315][NBIOT] UE specific DRX - FFSs (Huawei) | Huawei |
| R2-2004053 | Reply LS on Rel-16 NB-IoT enhancements | RAN2 |
| R2-2004054 | LS on UE specific DRX in NB-IoT | RAN2 |
| R2-2004057 | LS on SIB indication for UE specific DRX | RAN2 |
| 7.2.5 | NB-IoT UE capabilities | |
| R2-2002588 | Updates for Rel-16 additional enhancements NB-IoT | BlackBerry UK Limited |
| R2-2003248 | UE capabilities, TDD/FDD differentiation and 5GC applicability for NB-IoT and eMTC | Huawei, HiSilicon |
| R2-2004044 | Updates for Rel-16 additional enhancements NB-IoT | BlackBerry UK Limited |
| R2-2004048 | Report of [AT109bis-e][313][NBIOT] UE capabilities, TDD/FDD differentiation and 5GC applicability for NB-IoT and eMTC (Huawei) | Huawei |
| 7.2.6 | ASN.1 review of NB-IoT | |
| R2-2003250 | [H108][H109] TP on WUS sugnalling for per gap configuration | Huawei, HiSilicon |
| R2-2003251 | [H228][H229] TP on multipe TB schedullng in NB-IoT | Huawei, HiSilicon |
| R2-2003278 | Capture RRC setup using PUR | ZTE Corporation, Sanechips |
| R2-2004049 | Summary of [AT109bis-e][314][NBIOT] ASN.1 review of NB-IoT (Huawei) | Huawei |
| 7.3.1 | Organizational | |
| R2-2003262 | 36300CR for Introduction of Even futher Mobility enhancement in E-UTRAN | ChinaTelecom |
| R2-2003263 | UE Capability for Rel-16 LTE even further mobility enhancement | ChinaTelecom |
| R2-2003370 | UE Capability for Rel-16 LTE even further mobility enhancement | Intel Corporation |
| R2-2003777 | Correction on introduction of DAPS handover | China Telecommunications |
| R2-2003852 | Updates for R16 LTE Mobility Enhancements and LTE updates for R16 NR Mobility Enhancements | Ericsson |
| R2-2003858 | Correction on introduction of DAPS handover | China Telecommunications |
| 7.3.2.1 | Open issues and corrections for user plane aspects of DAPS HO | |
| R2-2002590 | Open issues for user plane aspects of DAPS HO | Ericsson |
| R2-2002608 | PDCP Status Reporting enhancements for DAPS DRBs | Qualcomm India Pvt Ltd |
| R2-2002737 | PDCP Status Report for UM DRBs in DAPS HO | MediaTek Inc. |
| R2-2002864 | Handling of compressed PDCP SDUs stored in reception buffer | LG Electronics Inc. |
| R2-2002868 | CR on 36.321 for LTE feMob | vivo |
| R2-2002869 | CR on 38.321 for NR mobility enhancement | vivo |
| R2-2002874 | Remaining user plane issues of DAPS | vivo |
| R2-2002953 | Discussion on PDCP status report for UM DRB | OPPO |
| R2-2002997 | Handling of security issue for DAPS without key change | NEC |
| R2-2003043 | PDCP CR on correction and outcome of [Post109e#11] for DAPS handover | Huawei, HiSilicon, Mediatek Inc. |
| R2-2003044 | PDCP CR on correction and outcome of [Post109e#11] for DAPS handover | Huawei, HiSilicon, Mediatek Inc. |
| R2-2003045 | Discussion on transmitting ROHC IR packets in target during DAPS HO | Huawei, HiSilicon, Vivo, Oppo, NEC, Apple, NTT DOCOMO INC., China Telecom |
| R2-2003330 | On Remaining Issues for DAPS UP | Nokia, Nokia Shanghai Bell |
| R2-2003665 | RoHC handling for inter-gNB and intra-gNB DAPS handover | SHARP Corporation |
| R2-2003845 | Report of [AT109bis-e][205][MOB] Flagging and discussion of DAPS UP open issues for PDCP/RLC/MAC (Huawei) | Huawei, HiSilicon |
| R2-2003853 | PDCP CR on correction and outcome of [Post109e#11] for DAPS handover | Huawei, HiSilicon, Mediatek Inc. |
| R2-2003854 | PDCP CR on correction and outcome of [Post109e#11] for DAPS handover | Huawei, HiSilicon, Mediatek Inc. |
| R2-2003855 | CR on 38.321 for NR mobility enhancement | vivo |
| R2-2003856 | CR on 36.321 for LTE feMob | vivo |
| 7.3.2.2 | Open issues and corrections for control plane aspects of DAPS HO | |
| R2-2002591 | Subsequent RRC Procedures after DAPS handover | Ericsson |
| R2-2002860 | Clean up the terminology for RRC and PDCP | LG Electronics Inc, Nokia, Nokia Shanghai Bell |
| R2-2002875 | Remaining control plane issues of DAPS | vivo |
| R2-2002952 | Correction on DAPS HO | OPPO |
| R2-2003046 | Discussion on control plane aspects of DAPS HO | Huawei, HiSilicon |
| R2-2003108 | Remaining control plane issues for DAPS | Nokia, Nokia Shanghai Bell |
| R2-2003371 | Report of 109b#11 open issues on DAPS | Intel Corporation |
| R2-2003372 | 38.331 CR on NR MOB | Intel Corporation |
| R2-2003502 | Discussion on network coordination and PHR report for DAPS HO | CMCC. |
| R2-2003530 | Indication of DAPS Handover Execution to the Source | ETRI |
| R2-2003846 | Report of [AT109bis-e][206][MOB] Flagging and discussion of DAPS CP open issues for RRC (Intel) | Intel Corporation |
| 7.3.2.3 | UE capabilities for DAPS HO | |
| R2-2002592 | Inter-node signalling for DAPS handover | Ericsson |
| R2-2002905 | Consideration on DAPS Capability | LG Electronics Inc. |
| R2-2003030 | UE capabilities for DAPS | Nokia, Nokia Shanghai Bell |
| R2-2003047 | Discussion on open issues for UE capability coordination | Huawei, HiSilicon |
| R2-2003367 | Discussion on capabilities for MOB | Intel Corporation |
| 7.3.4 | ASN.1 review of mobility WIs for LTE RRC | |
| R2-2003040 | Correction CR for conditional handover including RIL E901 | Ericsson |
| 7.6 | LTE TEI16 enhancements | |
| R2-2002887 | CR on RLC out-of-order delivery configuration | Samsung, LG Electronics Inc., Nokia, Nokia Shanghai Bell, Intel, Apple |
| R2-2002888 | LTE RLC out-of-order delivery configuration | Samsung, LG Electronics Inc., Nokia, Nokia Shanghai Bell, Intel, Apple |
| R2-2003842 | Summary of LTE contributions in AIs 7.4, 7.5, 7.6, 7.8 and 7.9 | Nokia (RAN2 vice-chair) |
| R2-2003860 | CR on RLC out-of-order delivery configuration | Samsung, LG Electronics Inc., Nokia, Nokia Shanghai Bell, Intel, Apple |
| R2-2003861 | CR on RLC out-of-order delivery configuration | Samsung, LG Electronics Inc., Nokia, Nokia Shanghai Bell, Intel, Apple |
| R2-2003862 | CR on RLC out-of-order delivery configuration | Samsung, LG Electronics Inc., Nokia, Nokia Shanghai Bell, Intel, Apple |
| R2-2003863 | CR on RLC out-of-order delivery configuration | Samsung, LG Electronics Inc., Nokia, Nokia Shanghai Bell, Intel, Apple |
| 7.7 | Support of Indian Navigation Satellite System (NavIC) | |
| R2-2003821 | Update missed out definition for Information Element NavModel-NavIC-KeplerianSet | Reliance Jio |
| R2-2003998 | Update missed out definition for Information Element NavModel-NavIC-KeplerianSet | Reliance Jio |
| 7.8 | DL MIMO efficiency enhancements for LTE | |
| R2-2003546 | Introduction of UE capabilities for DL MIMO efficiency enhancement | Huawei, Hisilicon |
| R2-2003547 | Introduction of UE capabilities for DL MIMO efficiency enhancement | Huawei, Hisilicon |
| 7.9 | LTE-based 5G Terrestrial Broadcast | |
| R2-2003364 | Correction on the configuration of subframe #0 and #5 for MCH in MBMS dedicated cell | Qualcomm Technologies Int |
| R2-2003544 | Discussion on MCCH configuration for 0.37kHz SCS | Huawei, Hisilicon |
| R2-2003545 | Clarification on MCCH configuration for 0.37kHz SCS | Huawei, Hisilicon |
| R2-2003864 | Clarification on MCCH configuration for 0.37kHz SCS | Huawei, Hisilicon |
| R2-2003866 | Correction on the configuration of subframe #0 and #5 for MCH in MBMS dedicated cell | Qualcomm Technologies Int |
| 8.1 | Session on LTE legacy, LTE TEI16 and NR/LTE Rel-16 Mobility | |
| R2-2003801 | Report from session on LTE legacy, LTE TEI16 and NR/LTE Rel-16 Mobility | Vice Chairman (Nokia) |
| 8.2 | Session on SRVCC, CLI, PRN, eMIMO, RACS | |
| R2-2003802 | Report from Break-Out Session on SRVCC, CLI, PRN, eMIMO, RACS | Vice Chairman (ZTE) |
| 8.3 | Session on eMTC | |
| R2-2003803 | Report eMTC breakout session | Session chair (Ericsson) |
| 8.4 | Session on NR-U, Power Savings, NTN and 2-step RACH | |
| R2-2003804 | Session minutes for NR-U, Power Savings, NTN and 2-step RACH | Session chair (InterDigital) |
| 8.5 | Session on Rel-15 and 16 LTE and NR positioning | |
| R2-2003805 | Report from session on Rel-15 and 16 LTE and NR positioning | Session chair (MediaTek) |
| 8.6 | Session on SON/MDT | |
| R2-2003806 | Report from SOM/MDT session | Session chair (CMCC) |
| 8.7 | Session on NB-IoT | |
| R2-2003807 | Report NB-IoT breakout session | Session chair (Huawei) |
| 8.8 | Session on LTE V2X and NR V2X | |
| R2-2003808 | Report from session on LTE V2X and NR V2X | Session chair (Samsung) |
| 9 | Reserved Numbers | |
| R2-2003865 | (reserved) | Tero's tdocs |
| R2-2003867 | (reserved) | Tero's tdocs |
| R2-2003890 | (reserved) | Tero's tdocs |
| R2-2003909 | (reserved) | Sergio's tdocs |
| R2-2003913 | (reserved) | Sergio's tdocs |
| R2-2003914 | (reserved) | Sergio's tdocs |
| R2-2003915 | (reserved) | Sergio's tdocs |
| R2-2003919 | (reserved) | Sergio's tdocs |
| R2-2003924 | (reserved) | Emre's tdocs |
| R2-2003938 | (reserved) | Emre's tdocs |
| R2-2003939 | (reserved) | Emre's tdocs |
| R2-2003943 | (reserved) | Emre's tdocs |
| R2-2003944 | (reserved) | Emre's tdocs |
| R2-2003945 | (reserved) | Emre's tdocs |
| R2-2003946 | (reserved) | Emre's tdocs |
| R2-2003947 | (reserved) | Emre's tdocs |
| R2-2003948 | (reserved) | Emre's tdocs |
| R2-2003949 | (reserved) | Emre's tdocs |
| R2-2003950 | (reserved) | Emre's tdocs |
| R2-2003974 | (reserved) | Diana's tdocs |
| R2-2003976 | (reserved) | Diana's tdocs |
| R2-2003977 | (reserved) | Diana's tdocs |
| R2-2003978 | (reserved) | Diana's tdocs |
| R2-2003979 | (reserved) | Diana's tdocs |
| R2-2003980 | (reserved) | Diana's tdocs |
| R2-2003999 | (reserved) | Nathan's tdocs |
| R2-2004000 | (reserved) | Nathan's tdocs |
| R2-2004006 | (reserved) | HuNan's tdocs |
| R2-2004007 | (reserved) | HuNan's tdocs |
| R2-2004008 | (reserved) | HuNan's tdocs |
| R2-2004009 | (reserved) | HuNan's tdocs |
| R2-2004010 | (reserved) | HuNan's tdocs |
| R2-2004011 | (reserved) | HuNan's tdocs |
| R2-2004012 | (reserved) | HuNan's tdocs |
| R2-2004013 | (reserved) | HuNan's tdocs |
| R2-2004014 | (reserved) | HuNan's tdocs |
| R2-2004015 | (reserved) | HuNan's tdocs |
| R2-2004016 | (reserved) | HuNan's tdocs |
| R2-2004017 | (reserved) | HuNan's tdocs |
| R2-2004018 | (reserved) | HuNan's tdocs |
| R2-2004019 | (reserved) | HuNan's tdocs |
| R2-2004020 | (reserved) | HuNan's tdocs |
| R2-2004021 | (reserved) | HuNan's tdocs |
| R2-2004022 | (reserved) | HuNan's tdocs |
| R2-2004023 | (reserved) | HuNan's tdocs |
| R2-2004024 | (reserved) | HuNan's tdocs |
| R2-2004025 | (reserved) | HuNan's tdocs |
| R2-2004026 | (reserved) | HuNan's tdocs |
| R2-2004027 | (reserved) | HuNan's tdocs |
| R2-2004028 | (reserved) | HuNan's tdocs |
| R2-2004029 | (reserved) | HuNan's tdocs |
| R2-2004030 | (reserved) | HuNan's tdocs |
| R2-2004031 | (reserved) | HuNan's tdocs |
| R2-2004032 | (reserved) | HuNan's tdocs |
| R2-2004033 | (reserved) | HuNan's tdocs |
| R2-2004034 | (reserved) | HuNan's tdocs |
| R2-2004035 | (reserved) | HuNan's tdocs |
| R2-2004059 | (reserved) | Brian's tdocs |
| R2-2004060 | (reserved) | Brian's tdocs |
| R2-2004061 | (reserved) | Brian's tdocs |
| R2-2004062 | (reserved) | Brian's tdocs |
| R2-2004063 | (reserved) | Brian's tdocs |
| R2-2004064 | (reserved) | Brian's tdocs |
| R2-2004065 | (reserved) | Brian's tdocs |
| R2-2004066 | (reserved) | Brian's tdocs |
| R2-2004067 | (reserved) | Brian's tdocs |
| R2-2004068 | (reserved) | Brian's tdocs |
| R2-2004069 | (reserved) | Brian's tdocs |
| R2-2004070 | (reserved) | Brian's tdocs |
| R2-2004080 | (reserved) | Kyeongin's tdocs |
| R2-2004088 | (reserved) | Kyeongin's tdocs |
| R2-2004089 | (reserved) | Kyeongin's tdocs |
| R2-2004090 | (reserved) | Kyeongin's tdocs |
| R2-2004091 | (reserved) | Kyeongin's tdocs |
| R2-2004092 | (reserved) | Kyeongin's tdocs |
| R2-2004093 | (reserved) | Kyeongin's tdocs |
| R2-2004094 | (reserved) | Kyeongin's tdocs |
| R2-2004095 | (reserved) | Kyeongin's tdocs |
| R2-2004096 | (reserved) | Kyeongin's tdocs |
| R2-2004097 | (reserved) | Kyeongin's tdocs |
| R2-2004098 | (reserved) | Kyeongin's tdocs |
| R2-2004099 | (reserved) | Kyeongin's tdocs |
| R2-2004100 | (reserved) | Kyeongin's tdocs |
| R2-2004103 | (reserved) | Nathan's tdocs |
| R2-2004104 | (reserved) | Nathan's tdocs |
| R2-2004105 | (reserved) | Nathan's tdocs |
| R2-2004106 | (reserved) | Nathan's tdocs |
| R2-2004107 | (reserved) | Nathan's tdocs |
| R2-2004108 | (reserved) | Nathan's tdocs |
| R2-2004109 | (reserved) | Nathan's tdocs |
| R2-2004110 | (reserved) | Nathan's tdocs |
| R2-2004111 | (reserved) | Nathan's tdocs |
| R2-2004112 | (reserved) | Nathan's tdocs |